Control: reassign -1 ifupdown On Sat, 4 Jul 2015 13:58:50 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 04.07.2015 um 11:38 schrieb Daniel Pocock: > > Package: systemd > > Version: 215-17+deb8u1 > > Severity: important > > > > This has been happening on a system that was upgraded from wheezy to jessie > > > > Sometimes systemd starts the network and then tries to start things that > > depend on the network (e.g. ntpdate, NFS client mounts) before DHCP has > > obtained a lease. > > > > Sometimes the boot completely stops and asks for root login > > > > Sometimes it reaches the X login but if a user logs in, it throws them > > out because their home is not mounted. > > Is home mounted via NFS? > > > journalctl also shows errors from other processes that depend on the > > network. > > > > > > Here is the content of /etc/network/interfaces - it was working fine > > with wheezy: > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > > > # The primary network interface > > allow-hotplug eth0 > > iface eth0 inet dhcp > > #iface eth0 inet6 auto > > iface eth0 inet6 dhcp > > accept_ra 1 > > > > #allow-hotplug eth1 > > #iface eth1 inet dhcp > > In the end this is a bug in ifupdown. It should ensure to block until > the network has been configured successfully. > > If you change "allow-hotplug" to "auto", does that help?
I'm going to re-assign this to ifupdown. But my understanding is, that allow-hotplug is supposed to be *non*-blocking. So you won't get any guarantees during boot. If you want that, you are supposed to use "auto". I'll let Guus comment if he intends to address that (with the ifupdown-wait-online idea we discussed a while ago), or if he simply considers that expected behaviour. Regards, Michael -- 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