Control: reassign -1 ifupdown Am 08.11.2014 um 18:20 schrieb Andrew Shadura: > reassign 766943 systemd > thanks > > I don't think it's right that the bug is assigned at ifupdown. > Neither ifupdown nor its init scripts make any assumptions regarding > init system being used, so I don't see how is it more helpful > to have me dealing with this, but not systemd maintainers. > I'd be happy to apply a fix if one appears at some point, but > to me it looks more like there's something elsewhere. >
allow-hotplug interfaces are configured when the actual hardware is available. For auto interfaces, ifupdown runs the /etc/init.d/networking init script and assumes that at the time the script runs during boot, those interfaces exist. If they don't exist, the networking init script fails to bring up those auto interfaces. That's the problematic bit. Afaics there is nothing in ifup or the networking init script which ensures, that those devices exist. This mode of operation is simply racy. And with systemd being much quicker and running more stuff in parallel during early boot, it's just more likely that the networking init script is run when the device is not yet available. My suggestion would be, to make "ifup -a" wait for all auto interfaces to become available with a configurable timeout (60 seconds seems like a good compromise) after which it gives up waiting for the devices, prints a warning and proceeds. Re-assigning this back to ifupdown, as this is not a systemd issue. -- 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
