Am 10.11.2014 um 04:08 schrieb Michael Biebl: > Am 10.11.2014 um 04:02 schrieb Christoph Anton Mitterer: >> Hey Michael... >> >> On Mon, 2014-11-10 at 03:40 +0100, Michael Biebl wrote: >>> allow-hotplug interfaces are configured when the actual hardware is >>> available. >> But you have seen what I've wrote previously,.. that I *do* in fact also >> have issues with allow-hotplug... so there most likely is something >> fishy there (or in unit files of services) as well.. >> So is this something that I should deal with in another bug? > > You are conflating two issues. > Bringing an interface up with ifup@.service is not racy, since it runs > when the hardware is actually added. *BUT* you lose the synchronisation > point that is /etc/init.d/networking, since ifup@.service can be > triggered at any time and doesn't delay boot. > SysV init script (or other services which depend on $network or > network.target) therefor have a problem with allow-hotplug.
To provide such a syncronisation point, i.e. having network.target and network-online.target [1] properly hooked up, I've implemented a PoC ifupdown-wait-online service. You can get it from [2] and enable it via "systemctl enable ifupdown-wait-online.service". This service is hooked up into network.target and network-online.target and blocks until one interface has been successfully configured or a timeout is reached. SysV init scripts which require $network will therefore be started after at least one interface has been configured, no matter if auto or allow-hotplug. As said, this is PoC and we can further discuss what "network up" actually is supposed to mean: one interface up, all interfaces up, etc. [1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ [2] https://people.debian.org/~biebl/ifupdown-wait-online.tar.gz -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
