Package: sysv-rc Version: 2.88dsf-59 Severity: normal Hi,
When a daemon is started by a systemd target, and not by the sysV runlevel, upgrading the package (which I presume runs invoke-rc.d to restart the daemon) stops the daemon and does not restart it. As an example, I do not want to start MariaDB until the cryptfs it uses is manually unlocked. The sysV system is configured to not start MariaDB, so that at boot it does not try to start and fail because the cryptfs is locked. After the cryptfs is unlocked MariaDB (and some other stuff) is started via a systemd target. The MariaDB package is supposed to restart the daemon, but instead with this configuration an upgrade stops the daemon and never restarts it. (So, something like cron-apt or unattended-upgrades is ungood.) I can't tell if this has to do with bug #768450 or not. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sysv-rc depends on: ii debconf [debconf-2.0] 1.5.56 ii insserv 1.14.0-5 ii startpar 0.59-3 ii sysvinit-utils 2.88dsf-59 Versions of packages sysv-rc recommends: ii lsb-base 4.1+Debian13+nmu1 Versions of packages sysv-rc suggests: pn bum <none> -- debconf information: sysv-rc/unable-to-convert:
