[Bug 1627769] Re: limits.conf not applied

[Adam Dingle]

OK - I was finally able to get this working in 17.04 after more
experimentation, which revealed the following caveats:

- Ubuntu will respect limits you put in /etc/security/limits.conf (or
/etc/security/limits.d/audio.conf), but **only after a reboot**.
Logging out and back in are not sufficient to trigger a change.  I
suspect that rebooting only became necessary after the recent transition
to systemd.

- Limits in /etc/systemd/user.conf are applied after logging out and in.

- I've only been able to change NOFILE (the max number of open files) by
editing /etc/systemd/system.conf and then rebooting (logging out/in is
not enough).  Setting this value in user.conf or limits.conf seems to
have no effect.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1627769

Title:
  limits.conf not applied

Status in jackd2 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio     99
  @audio   -  memlock    unlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack at ideaon:~$ ulimit -l -r
  max locked memory       (kbytes, -l) 64
  real-time priority              (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack at ideaon:~$ ulimit -l -r
  max locked memory       (kbytes, -l) 64
  real-time priority              (-r) 0
  blablack at ideaon:~$ su blablack
  Password: 
  blablack at ideaon:~$ ulimit -l -r
  max locked memory       (kbytes, -l) unlimited
  real-time priority              (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1627769/+subscriptions