Bug#803013: systemd should not destroy application created cgroups

[paul.szabo at sydney.edu.au]

Dear Michael,

>>>> I wonder how that line came to be missed on my machines ...
> If you restore the previous state and you ran
> dpkg-reconfigure libpam-runtime, what do you get?

Running
  dpkg-reconfigure libpam-runtime
asks me nicely:

  PAM configuration
  
  Pluggable Authentication Modules (PAM) determine how authentication,
  authorization, and password changing are handled on the system, as
  well as allowing configuration of additional actions to take when
  starting user sessions.
  
  Some PAM module packages provide profiles that can be used to
  automatically adjust the behavior of all PAM-using applications on the
  system.  Please indicate which of these behaviors you wish to enable.
  
  PAM profiles to enable:
  
     [*] Unix authentication
     [ ] Register user sessions in the systemd control group hierarchy
     [ ] GNOME Keyring Daemon - Login keyring management
     [ ] Inheritable Capabilities Management
  
     <Ok>       <Cancel>

There is no indication that I should, or must, select "do systemd".

>> There is also a file
>>   /etc/pam.d/common-session-noninteractive
>> that does not contain the pam_systemd.so line, used for cron and sudo
>> (maybe others): can cgroups be used for or from those?

I wonder.

> I'm not sure what to do about this bug report. I'm inclined to close
> it, since it doesn't look like something which we can address in
> systemd itself.

I believe my patch would make systemd more robust, that may help to
prevent future recurrences of this bug.

Cheers, Paul

Paul Szabo   psz at maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of Sydney    Australia