Package: systemd Version: 204-14 Severity: normal File: /bin/systemctl Hi,
While in systemd 204 reloading a service that is stopped is a noop and exits with zero: # systemctl stop virtlockd.service && systemctl reload virtlockd.service ; echo $? Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket 0 It exits nonzero with 208: # systemctl stop virtlockd.service && systemctl reloadvirtlockd.service ; echo $? Warning: Stopping virtlockd.service, but it can still be activated by: virtlockd.socket Job for virtlockd.service failed. See 'systemctl status virtlockd.service' and 'journalctl -xn' for details. 1 This broke libvirt-daemon-system which relied on the 204 behaviour. I've worked around this in the postinst but there's potential for more breackage on users systems. The 204 behaviour should probably be restored. Cheers -- Guido -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-rc6 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.3 ii libacl1 2.2.52-1 ii libaudit1 1:2.3.7-1 ii libc6 2.19-7 ii libcap2 1:2.24-4 ii libcap2-bin 1:2.24-4 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.6-1 ii libgcrypt11 1.5.4-2 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 204-14 ii libsystemd-journal0 204-14 ii libsystemd-login0 204-14 ii libudev1 208-6 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.3 ii udev 208-6 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: ii libpam-systemd 204-14 Versions of packages systemd suggests: pn systemd-ui <none> -- Configuration Files: /etc/systemd/logind.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
