[Touch-packages] [Bug 2044034] Re: /etc/security/limits.conf memlock changes have no effect
** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2044034 Title: /etc/security/limits.conf memlock changes have no effect Status in pam package in Ubuntu: Invalid 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. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044034] Re: /etc/security/limits.conf memlock changes have no effect
This ticket can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2044034 Title: /etc/security/limits.conf memlock changes have no effect Status in pam package in Ubuntu: New 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. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044034] Re: /etc/security/limits.conf memlock changes have no effect
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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2044034 Title: /etc/security/limits.conf memlock changes have no effect Status in pam package in Ubuntu: New 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. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044034] Re: /etc/security/limits.conf memlock changes have no effect
This also fails... meaning... ulimit -l as root still shows 64... *- memlock unlimited root - memlock unlimited -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/2044034 Title: /etc/security/limits.conf memlock changes have no effect Status in pam package in Ubuntu: New 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. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
