/etc/security/limits.conf memlock changes have no effect

Bug #2044034 reported by David Favor
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pam (Ubuntu)

Bug Description

APT reports package as libpam-modules + launchpad says pam is the closest package. Please change package name, if required.

Summary says it all.

Default of memlock seems to be 64 (which limits.conf suggests means 64k). Changing this setting seems to have no effect.

The following entry seems to be correct, and has no effect after reboot, meaning ulimit -l still reports 64. I've tried 128, -1, unlimited, nothing seems to work.

Maybe I just misunderstand the correct settings or maybe Ubuntu overrides limits.conf at boot time.

My entry...

* - memlock unlimited

Be great if someone can help me fixing this, as likely it's a simple config file fix somewhere.


Revision history for this message
David Favor (davidfavor) wrote :

This also fails... meaning... ulimit -l as root still shows 64...

* - memlock unlimited
root - memlock unlimited

Revision history for this message
David Favor (davidfavor) wrote :

Looks like the problem was UsePAM=yes in /etc/ssh/sshd_config.

So system wide memlock is effected + ssh logins only effected if PAM is enabled to set limits.

Revision history for this message
David Favor (davidfavor) wrote :

This ticket can be closed.

Steve Langasek (vorlon)
Changed in pam (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.