[Pkg-systemd-maintainers] Bug#731803: Bug#731803: dh-systemd: dh_installinit and dh_systemd_start are both present when using symlink instead of Alias
Michael Stapelberg
stapelberg at debian.org
Wed Dec 25 09:38:02 GMT 2013
control: tags -1 + pending
Hi Laurent,
Laurent Bigonville <bigon at debian.org> writes:
> After switching from Alias= to mask the SysV initscript to a symlink, it
> seems that my service is (re)started twice, once with the snippet added
> by dh_installinit and the second time by dh_systemd_start.
> dh_systemd_start doesn't seems to detect that dh_installinit is already
> taking care of the same service.
>
> # Automatically added by dh_installinit
> if [ -x "/etc/init.d/nut-client" ]; then
> update-rc.d nut-client defaults >/dev/null
> if [ -n "$2" ]; then
> _dh_action=restart
> else
> _dh_action=start
> fi
> invoke-rc.d nut-client $_dh_action || exit $?
> fi
> # End automatically added section
> # Automatically added by dh_systemd_start
> if [ -d /run/systemd/system ]; then
> systemctl --system daemon-reload >/dev/null || true
> deb-systemd-invoke try-restart nut-monitor.service >/dev/null || true
> fi
> # End automatically added section
>
> This might be a problem for some service I guess
Thanks for the report. I have addressed this issue with commit
http://anonscm.debian.org/gitweb/?p=collab-maint/init-system-helpers.git;a=commitdiff;h=51f7ec85551720b9cf80797996e3656e75e4e18c
Can you verify that this commit fixes the problem for you? I’ll upload a
new version then.
Thanks!
--
Best regards,
Michael
More information about the Pkg-systemd-maintainers
mailing list