setting core dump size to above 0 does not work in /etc/security/limits.conf
Bug #314222 reported by
LimCore
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
High
|
Steve Langasek | ||
Jaunty |
Fix Released
|
High
|
Steve Langasek |
Bug Description
Ubuntu 8.04 amd64
ii libpam-modules 0.99.7.1-5ubuntu6.1
Hi, after setting:
$ grep core /etc/security/
# - core - limits the core file size (KB)
* hard core 409600
* soft core 102400
#* soft core 0
and rebooting,
I get ulimit -a
core file size (blocks, -c) 0
for both the root ( as written in bug#65244 )
and for the users - this seems like a bug to me.
Related branches
Changed in pam: | |
status: | Confirmed → In Progress |
Changed in pam: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
These limits work as they should for users in Intrepid 8.10 amd64.
I don't have an 8.04 Hardy server to test with. It would be
good to have someone else independently verify this issue on 8.04 Hardy.
Note that for root limits you need to specify the root username:
root hard core 409600
root soft core 102400
per bug #65244 which I created a path to fix (just
improved documentation) for some months back.
Jonathan