Actually, the line I already posted was the whole non-comment content of my /etc/security/limits.conf. I'm logging in to the machine where I noticed the problem via ssh, so I guess this determines the PAM service used. I switched to a 2.6.29 kernel, but the problem persists.
I also reproduced the problem on another machine with a much newer Debian installation (also squeeze) and a stock kernel (the other one was manually built), as follows: 1. Login on console (as user kraft), "ulimit -l" gives 64, logout 2. Add one line to the (pristine) /etc/security/limits.conf: kraft hard memlock 10000 3. Login on console, "ulimit -l" still gives 64, logout 4. aptitude install libpam-modules=1.0.1-5+lenny1 (denying the modification of /etc/security/limits.conf) 5. Login on console, "ulimit -l" now gives 10000 Any ideas about what else I can do to isolate the source of the problem? Daniel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
