Ubuntu 11.10 waiting up to 60 more seconds for network configuration 'problem'

-->
I upgaded my ubuntu 11.04 Natty to ubuntu 11.10 Oneiric Ocelot a few weeks ago. To handle some issues I have needed to modify /etc/network/interfaces file. After some modifations I get the message:"waiting up to 60 more seconds for network configuration" when booting.
I have found the reason of this is to have any interfaces in /etc/network/interface file as auto. To correct the problem just remove all rows and leave it as default like:

auto lo iface lo inet loopback

Another solution can be modify the script /etc/init/failsafe.conf>>This script is the script that control configuration of network interfaces when booting and if they are not all configured send the message above to the screen.. So let's take a look at that script:

# failsafe description "Failsafe Boot Delay" author "Clint Byrum <clint@ubuntu.com>" start on filesystem and net-device-up IFACE=lo stop on static-network-up or runlevel console output script # Determine if plymouth is available if [ -x /bin/plymouth ] && /bin/plymouth --ping ; then PLYMOUTH=/bin/plymouth else PLYMOUTH=":" fi # The point here is to wait for 2 minutes before forcibly booting # the system. Anything that is in an "or" condition with 'started # failsafe' in rc-sysinit deserves consideration for mentioning in # these messages. currently only static-network-up counts for that. sleep 5 # Plymouth errors should not stop the script because we *must* reach # the end of this script to avoid letting the system spin forever # waiting on it to start. $PLYMOUTH message --text="Waiting for network configuration..." || : sleep 10 $PLYMOUTH message --text="Waiting up to 10 more seconds for network configuration..." || : sleep 10 $PLYMOUTH message --text="Booting system without full network configuration..." || : # give user 1 second to see this message since plymouth will go # away as soon as failsafe starts. sleep 1 exec initctl emit --no-wait failsafe-boot end script post-start exec logger -t 'failsafe' -p daemon.warning "Failsafe of 120 seconds reached."

As we see and understood from the scripts commands: that script is controlling the waiting duration when booting.. The script keeps waiting us totally 111 seconds.. If your system doesn't need to wait  just insert a # character at the beginning of sleep calls or remove these rows. If your system needs to wait, but you don't wanna be wait this much, just change the values as you want.. Problem solved in either ways, but I recommend the first one..

Note: The values of sleep calls in your script may be different than my script, that is because of I have made a modification before in that script..
In my case, I solved my problem with two ways. In the second way the final look of my failsafe.conf script is given in the following:

# failsafe description "Failsafe Boot Delay" author "Clint Byrum <clint@ubuntu.com>" start on filesystem and net-device-up IFACE=lo stop on static-network-up or runlevel console output script # Determine if plymouth is available if [ -x /bin/plymouth ] && /bin/plymouth --ping ; then PLYMOUTH=/bin/plymouth else PLYMOUTH=":" fi # The point here is to wait for 2 minutes before forcibly booting # the system. Anything that is in an "or" condition with 'started # failsafe' in rc-sysinit deserves consideration for mentioning in # these messages. currently only static-network-up counts for that. sleep 5 # Plymouth errors should not stop the script because we *must* reach # the end of this script to avoid letting the system spin forever # waiting on it to start. $PLYMOUTH message --text="Waiting for network configuration..." || : sleep 10 $PLYMOUTH message --text="Waiting up to 10 more seconds for network configuration..." || : sleep 10 $PLYMOUTH message --text="Booting system without full network configuration..." || : # give user 1 second to see this message since plymouth will go # away as soon as failsafe starts. sleep 1 exec initctl emit --no-wait failsafe-boot end script post-start exec logger -t 'failsafe' -p daemon.warning "Failsafe of 120 seconds reached."

-->

If you have any question, or need some help leave a comment below..