[Bug 916890] Re: "Waiting for network configuration" on every boot
stgraber at stgraber.org
Tue Jan 17 15:45:47 UTC 2012
Ok, I just confirmed it by looking at the changelog actually:
* Stop on run-parts failure (Closes: #547587).
So if any of the scripts fails, ifupdown will stop processing the
I'd suggest you change your scripts to either not fire if it's not the
right interface or simply change these exit 1 to an exit 0 + logging so
it doesn't block the interface from being initialised but you'll still
now it failed.
I'm marking this bug as Invalid as it was actually an upstream bugfix
causing that change in behaviour.
Thanks for all your help in tracking this one down.
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Invalid
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
"Waiting for network configuration" on every boot
Status in “ifupdown” package in Ubuntu:
Upgrade from 0.7~alpha5.1ubuntu6 to 0.7~beta2ubuntu1 brought this on:
on every boot the "Waiting for network configuration" and "Waiting up
to 60 seconds more for network" messages appear and boot is thus about
2 minutes slower than before. It also says it's booting without
network, but the network is in fact there after I log in.
Downgrading back to 0.7~alpha5.1ubuntu6 makes the wait go away again.
Reproduced this on three different computers on two different
networks, both wired and wireless.
DistroRelease: Ubuntu 12.04
Package: ifupdown 0.7~beta2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic i686
Date: Sun Jan 15 21:10:34 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
UpgradeStatus: Upgraded to precise on 2011-12-09 (37 days ago)
To manage notifications about this bug go to:
More information about the foundations-bugs