Package: pdnsd Version: 1.2.9a-par-3 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: insserv-removal
Hi, your package pdnsd ships a insserv.conf configuration in /etc/inserv.conf.d/ or is listed in /etc/insserv.conf to provide the $named LSB/SysV facility. The $named facility is typically defined when full host/network name resolution is available. Other SysV init scripts depending on $named are ordered after your service then. Under systemd the $named facility is mapped to the nss-lookup.target, see [1] for more details. The equivalent to the insserv configuration under systemd is pulling in nss-lookup.target and ordering your service before that target. This dependency is currently being automatically generated via a generator [2], but this requires an intrusive patch which we would like to drop. So instead we would like services to declare this dependency explicitly. If your package already ships a native .service file, please add the following to the [Unit] section: Wants=nss-lookup.target Before=nss-lookup.target If your package does not yet ship a native .service file, this would be a good occasion to do so and the Debian pkg-systemd team is glad to assist you. But you can also extend SysV init scripts with that information using the drop-in mechanism [3]. For an SysV init script named /etc/init.d/foo, you create a directory /lib/systemd/system/foo.service.d/ and a place a .conf file in there. In this case I would suggest naming it named.conf, which would make it /lib/systemd/system/pdnsd.service.d/named.conf This file should contain: [Unit] Wants=nss-lookup.target Before=nss-lookup.target If you have further questions please don't hesitate to ask. Thanks for considering. Michael, on behalf of the pkg-systemd team. [1] https://www.freedesktop.org/software/systemd/man/systemd.special.html#nss-lookup.target [2] https://www.freedesktop.org/software/systemd/man/systemd.generator.html [3] https://www.freedesktop.org/software/systemd/man/systemd.unit.html