Package: sysv-rc Version: 2.88dsf-51 Severity: minor Dear Maintainer,
when invoke-rc.d is called under systemd, it doesn't even tell the user that a service has been started/stopped/restarted. This is surprising, especially considering that invoke-rc.d is used by maintainer scripts: When I re-installed a package I was working on, I wondered why the service had not been restarted the way it used to be. Using "systemctl status", I noticed that it actually *had* been restarted, but it didn't tell me. To reproduce, run invoke-rc.d postfix reload or anything similar. On a sysvinit system, this prints [ ok ] Reloading Postfix configuration...done. while on a systemd system, it prints nothing. Kind regards Ralf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sysv-rc depends on: ii debconf [debconf-2.0] 1.5.52 ii insserv 1.14.0-5 ii sysvinit-utils 2.88dsf-51 Versions of packages sysv-rc recommends: ii lsb-base 4.1+Debian12 Versions of packages sysv-rc suggests: pn bum <none> pn sysv-rc-conf <none> -- debconf information: sysv-rc/unable-to-convert: sysv-rc/convert-legacy: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org