ulimits not set according to /etc/security/limits.conf for root - update documentation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
Medium
|
Jonathan Marsden | ||
Bug Description
Binary package hint: libpam-modules
Hello, I am desperately trying to allow root big or unlimited coredumps. I set "* soft core 102400" and "* hard core 102400" in /etc/security/
I also tried to add pam_limits.so to /etc/pam.
If this is not a bug in PAM but only my inability to find the right solution, please consider it a documentation bug report. It prevent us from debugging crashing gdm daemon (see
http://
Thanks, Vaclav Smilauer
Changed in pam: | |
importance: | Undecided → Medium |
Thanks for your report. As you said this is not a bug in pam but a documentation issue. limits. conf):
The fact to allow explicitly allow limits for user root has been addressed a while ago (30 Aug 2000) but you need to explicitly name user root to apply the limits.
For example (/etc/security/
* soft core 0
root soft core 0
The first line doesn't affect superuser (zero core dump size), but the second one does.
Group and default limits aren't processed, per-user limits get applied even if the user is root.