Beck, Andre [2014-06-01 16:24 +0200]:
Pondering this a bit more, I've changed my copy in /etc/systemd/system
to now read
WantedBy=sysinit.target
as this is reflecting better where Debian has placed networking and
resolvconf traditionally - in rcS.d.
Right, agreed.
The attached debdiff adjusts the WantedBy and cleans up the symlinks
on upgrade. It's not actively harmful to have two, but it might look a
bit confusing. Note that systemctl reenable also works when systemd
is not running, thus the postinst only checks if the systemctl command
exists.
I think the additional explicit Before=networking.service (and possibly
others) is also necessary since networking is also ordered before
sysinit.target.
Thinking about it slightly more, what is really needed (for the
networking/ifupdown case) is to ensure that resolvconf.service is started
before any invocation of ifup, including by hotplugging/udev.
As far as I can work out, even with sysv-rc there's a potential race for
hotplugged interfaces to be started before the resolvconf init script. Has
this already been solved somehow? Does ifupdown defer hotplugged
configuration until after the networking script? I can't see any such
mechanism..
There used to be an ifupdown(.sh?) init script but I can't remember
precisely what that did.
--
Edward Allcutt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
