Package: libpam-modules Version: 1.1.1-6.1 Severity: normal Hi,
> I have tested and confirmed that this is fixed in squeeze. I believe the > actual fix was the change in version 1.0.1-9 to fix Ubuntu bug #314222, > describing a similar issue as this one. Marking this bug as resolved. Actually, it appears to not be fixed in squeeze. I was looking in the changelog to entries related to 'pam_limits' and found contradictory documentation and behaviour: 1) man 8 pam_limits says "Users of uid=0 are affected by this limits" 2) man 5 limits.conf adds this general note on PAM: NOTE: group and wildcard limits are not applied to the root user. To set a limit for the root user, this field must contain the literal username root. And in practice this is the only way to make 'nofile' limit work, by duplicating the wildcard limit for 'root' (see my config below). However, Steve says that this should work in squeeze with the wildcard '*' and this is confusing. I would also like to add that '*' works just fine on RHEL for root too (no need to duplicate the 'nofile' limit just for the root user). Thanks -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-modules depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l ii libselinux1 2.0.96-1 SELinux runtime shared libraries libpam-modules recommends no packages. libpam-modules suggests no packages. -- Configuration Files: /etc/security/limits.conf changed: * - nofile 65536 root - nofile 65536 -- debconf information: libpam-modules/disable-screensaver: -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
