Hi Thomas,
On Mon, 23 Jun 2014, Thomas Hood wrote:
I think it just needs to be tested. Have you tested the proposed fix at
all?
I've been using the below minimal patch locally for a few weeks now. It
works for me in the just-plain-ifupdown configuration use-case.
======================================
$ diff -u /lib/systemd/system/resolvconf.service /etc/systemd/system/resolvconf.service
--- /lib/systemd/system/resolvconf.service 2014-06-23 14:24:03.306557959 +0100
+++ /etc/systemd/system/resolvconf.service 2014-06-23 14:17:55.006474686
+0100
@@ -2,6 +2,7 @@
Description=Nameserver information manager
Documentation=man:resolvconf(8)
DefaultDependencies=no
+Before=networking.service
[Service]
RemainAfterExit=yes
@@ -11,4 +12,4 @@
ExecStop=/sbin/resolvconf --disable-updates
[Install]
-WantedBy=network.target
+WantedBy=sysinit.target
======================================
nb. WantedBy=sysinit.target matches the "Default-Start: S" from the old
init script and Before=networking.service corresponds to
"X-Start-Before: networking".
My earlier waffling about hotplugging is about a potential problem (which
I'm not sure really exists). It shouldn't block this bug from being
resolved.
--
Edward Allcutt
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
