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?
> 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. Uhm... I though systemd would at a certain point run networking.service via LSB compatibility (i.e. /etc/init.d/networking), and that in turn runs ifup? > 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. From the systemd side: What the long term goals in the sense of: If a service needs networking, but networking didn't start, the service isn't even tried to be started? Or even more detailed: If service postfix, needs eth3, but that didn's show up, and wasn't configured,.. postfix won't start either. Cause if things are ever to be going in such direction, than exiting ifup (and ultimately networking) with a timeout, would of course somehow need to communicate something like "hey systemd, eth0 and eth3 failed to come up, but wlan0 just went up fine". Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
