Package: systemd-shim Version: 9-1 Severity: normal Dear Maintainer,
when using sysvinit as PID1 and systemd-shim in conjunction with libpam-systemd starting (or restarting) daemons using service, invoke-rc.d, ifupdown hooks and initscripts directly place the daemons in question inside the cgroups of the current logind session. This causes the session to linger in the closing state after logout until the "misplaced" daemons are terminated. Also, due to #756247 it's not even possible to find out what daemons are "misplaced" because loginctl would not show the process tree of any user/session. The only workaround I found so far is breaking out of the session cgroups using cgm movepidabs all / $$ before performing any administrative action which could result in a background process being left behind (either by an initscript or an ifupdown hook). Regards, M. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-shim depends on: ii cgmanager 0.33-2 ii libc6 2.19-13 ii libglib2.0-0 2.42.1-1 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-15 -- no debconf information
signature.asc
Description: OpenPGP digital signature
