[Bug 893765] Re: boot hang when network cable is unplugged and /etc/network/interfaces used
Stéphane Graber
stgraber at stgraber.org
Thu Jun 28 20:55:11 UTC 2012
This is the expected behaviour, we have a timeout at 2 minutes though
since 11.10.
Quite a few systems require almost a minute for the link to appear, so
there's no way we can reliably depend on that. As for cases where the
interface doesn't exist, on quite a few system, it just doesn't exit
"yet". New systems with an impressive number of network cards can take
minutes before the kernel creates the network card.
** Changed in: ifupdown (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/893765
Title:
boot hang when network cable is unplugged and /etc/network/interfaces
used
Status in “ifupdown” package in Ubuntu:
Won't Fix
Bug description:
Steps to reproduce:
(deinstall networkmanager and) setup network interface to use dhcp (like auto eth0; iface eth0 inet dhcp)
unplug the network cable from the interface (eth0 in this case)
boot
expected result: system skips interface configuration and gives error immediately, because no link is NO LINK.
actual result: Boot hangs for something like 4 minutes, waiting for the cable to levitate to the socket magically.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/893765/+subscriptions
More information about the foundations-bugs
mailing list