Bug#825913: systemd init script integration: needs manual systemctl daemon-reload after installing initscript

Michael Biebl biebl at debian.org
Tue May 31 11:41:00 BST 2016


Am 31.05.2016 um 12:16 schrieb Chris Wilson:
> Jessie's 40-systemd script automatically invokes "systemctl daemon-reload" but
> only when run from a dpkg install. Even this backwards-compatibility measure
> seems to have been removed in unstable.

This is correct. Nowadays invoke-rc.d calls daemon-reload, so doing it
twice is a bit excessive.

> Please consider invoking "systemctl -p LoadState show $service" from 40-systemd,
> and if it says "not-found" then run "systemctl daemon-reload" to generate a
> service file for it.

I think in a case like yours, where the package manager is not involved,
doing an implicit reload for not-found in the lsb hook makes sense.
After all, we are pretty sure the sysv init script actually exists. So
the missing generated service file is indeed a pretty good indicator for
a missing daemon-reload.

So something like the attached patch?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: reload.patch
Type: text/x-patch
Size: 793 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160531/a0c32981/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160531/a0c32981/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list