So i'm just going to add on here instead of opening a new bug report. The problem is that in most cases when you're setting the limits, you're doing so for a process/user that isn't going to login. So the default is to set it in login, cron, sshd, su etc. Unfortunately, for a process that isn't going to login via normal methods. Such as a server process or the like this will be ignored because pam_limits.so will never be activated.
We need to put pam_limits.so in /etc/pam.d/common-session and /etc/pam.d /common-session-noninteractive as required by default, or, update the documentation somewhere that notes that limits.conf will not be activated by pam_limits.so otherwise. Since everything is already commented out by limits.conf per default it should be a straight-forward change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627769 Title: limits.conf not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1627769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
