Bug#803013: systemd should not destroy application created cgroups

[Michael Biebl]

Am 2015-11-07 04:22, schrieb 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".


The default should be, that all those 3 are selected. So definitely 
something odd.