Package: sysv-rc Version: 2.88dsf-58 Severity: important X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org
Hi, I'm currently working on the next version of FusionForge, which installs a new service in /etc/init.d/ and starts it as part of the installation process. So I: - Installed a new Debian 8 - git clone'd FusionForge and installed it - Ran 'make post-install' which: -- installs /etc/init.d/fusionforge-systasksd -- detects Debian (not RedHat) and registers it using 'update-rc.d' -- restarts the service using 'service fusionforge-systasksd restart' (note: same result with 'invoke-rc.d fusionforge-systasksd restart') Result: Failed to start fusionforge-systasksd.service: Unit fusionforge-systasksd.service failed to load: No such file or directory. Expected: /etc/init.d/fusionforge-systasksd is executed After searching the web to understand why on earth systemd dropped compatibility with init.d, I eventually got advice from #debian-systemd to just 'systemctl daemon-reload'. It seems that update-rc.d does not tell systemd about the new init.d script (and that invoke-rc.d only does so when $DPKG_MAINTSCRIPT_PACKAGE is set). FusionForge follows the Debian way to install and activate a service, hence I expect it works without having to introduce init-system-specific handling. So, I suggest that update-rc.d tells systemd about the new init script it just activated. CC-ing pkg-systemd-maintain...@lists.alioth.debian.org as per request on IRC :) Cheers! Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
