tags 524999 moreinfo unreproducible thanks On Tue, Apr 21, 2009 at 02:08:15PM +0200, Daniel Kraft wrote:
> I have a manually changed setting for memlock in /etc/security/limits.conf: > myself hard memlock 100000 > After upgrading to 1.0.1-9 (maybe already with 1.0.1-7, though I > didn't notice) this setting was ignored and the default of 64K used > instead. Downgrading to 1.0.1-5+lenny1 (without changing limits.conf > or anything else) fixed the problem. I have quite specifically tested pam_limits with memlock prior to this upload, and cannot reproduce the problem in question. Please post your full /etc/security/limits.conf file. Also, what PAM service are you seeing this with? Finally, the reportbug template shows that you're running a pre-lenny kernel. Does this problem persist if you upgrade to the lenny release kernel (or at least, to 2.6.26)? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
