Tom Horsley writes:
On Sun, 5 Nov 2017 14:19:47 -0800
Mike Wright wrote:
> I like that. Maybe something like a "systemd-networkd-wait-online.d
> directory that contains files named for the interfaces that have to be
> up and IP'd.
Then you find everything stops working when you get another
kernel update that breaks the unique interface naming
scheme and changes the names of all the interfaces (which
seems to happen with remarkable frequency).
How about just this: Wait for every damn interface that
is marked as "start on boot". Ignore all the other ones.
I have a better idea. How about "network-wait-online.service, or whatever
it's called, and whatever other services that need to be enabled, are
enabled by default".
If a service, like privoxy, requires all interfaces to be up, then it simply
needs to specify "network-wait-online" as a prerequisite, in its service
file, and that's the end of it. Full stop. No other action should be needed.
If nothing requires network-wait-online, well, nothing waits for all network
interfaces to be up. And if something does, this gets done, without
remembering whatever voodoo one needs to execute in order to make the system
actually work.
Is that really such a novel concept?
If a package, such as privoxy, gets installed, and configured according to
its instructions, but then it fails to start properly sometimes, then it's a
bug that needs to be fixed.