Package: systemd-sysv
Version: 228-4
Severity: important
If sysvinit-core is the active PID 1 and systemd-shim is installed and
running, installing systemd-sysv will lead to an unclean shutdown and a
dirty file system on the next boot.
Afaics, the problem is, that /sbin/{reboot,poweroff,shutdown} as shipped
by systemd-sysv does not talk to PID 1 via /run/initctl but uses D-Bus
if the org.freedesktop.systemd1 D-Bus name is taken, which is the case
if systemd-shim is installed.
Purging systemd-shim and stopping the systemd-shim process leads to
clean shutdown.
One could argue, that this is a bug in systemd-shim, which should be
able to shutdown/reboot the system cleanly when requested by tools
provided by systemd-sysv.
I'm filing this against systemd-sysv for now though, Maybe there is a
way how we can workaround this in systemctl, like say in
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L7425
add a check for sd_booted before trying to talk to systemd via D-Bus.
Michael
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd-sysv depends on:
ii systemd 228-4
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
