[Resolvconf-devel] Bug#847440: Bug#847440: resolvconf: run resolvconf service before any networking service

[Ryan Harper]

Hi,

I've tested in sid on amd64.

Before the change, I can see resolvconf runs before networking:

root at dear-alien:~# systemd-analyze critical-chain network-online.target
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.

└─network.target @290ms
  └─networking.service @94ms +195ms
    └─resolvconf.service @77ms +15ms
      └─system.slice @53ms
        └─-.slice @49ms

After the change, the order is right and also includes the
network-pre.target
Which means, if I switch to NetworkD or NetworkManager, resolvconf still
runs before them.

root at dear-alien:~# systemd-analyze critical-chain network-online.target
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.

└─network.target @259ms
  └─networking.service @58ms +199ms
    └─network-pre.target @55ms
      └─resolvconf.service @37ms +16ms
        └─system.slice @35ms
          └─-.slice @31ms


On Thu, Dec 8, 2016 at 12:19 PM, Thomas Hood <jdthood at gmail.com> wrote:

> Hi and thanks for the patch. Did you test it in Debian?
>
> --
> Thomas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/resolvconf-devel/attachments/20161208/5093e21c/attachment.html>