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.
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.