Thanks for your report. As you said this is not a bug in pam but a
documentation issue.
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/limits.conf):
* 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.
** Changed in: pam (Ubuntu)
Status: New => Confirmed
--
ulimits not set accrding to /etc/security/limits.conf for root
https://bugs.launchpad.net/bugs/65244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
