[Bug 839595] Re: failsafe.conf's 30 second time out is too low

[Clint Byrum]

Excerpts from ilf's message of Sun Oct 23 13:05:31 UTC 2011:
> The workaround only fixes the waiting time.
> It disables auto-up of the interface, which I want, if it us plugged in. This is a regression and still a major annoyance for me.
> Closing this bug report is not right, this isn't the fault of ifupdown, but upstart.
> 

ilf, this was an intentional change in behavior and documented in the
release notes. I understand it has made your particular use case a
bit more difficult to achieve. I do see a need for a second group in
/etc/network/interfaces called something like auto-nowait that will
be brought up at boot time but not waited on. I would encourage you to
open a new bug report as a feature request for this. Its a corner case,
but one that I think we can support for you as a user. Even better, you
can probably submit a patch and we should be able to add it for 12.04.

You can achieve it yourself by changing the line in
/etc/network/interfaces

from

auto eth0

to

allow-nowait eth0

and then edit /etc/init/network-interface.conf to run

ifup --allow nowait $IFACE

Just before the exec of ifup.

This will ensure that your interface is brought up, but not waited on
in the boot sequence.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/839595

Title:
  failsafe.conf's 30 second time out is too low

Status in Release Notes for Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released

Bug description:
  **** RELEASE NOTES ****

  If a system has network interfaces defined in /etc/network/interfaces
  as "auto", the operating system will wait up to 120 seconds for those
  interfaces to be fully detected and configured before continuing to
  boot the system. Most users of Ubuntu will not be affected by this
  change, as only servers and dedicated workstations should have network
  interfaces configured in this way.

  ************************

  as far as I can understand, the 30 second sleep in failsafe.conf means
  that /etc/init/rc-sysinit.conf will start within at most 30 seconds of
  'filesystem' and 'ifup lo' having occurred.

  I think that is really to small a number.   You're only safeguarding
  against the case where a user had an entry in /etc/network/interfaces
  that where the device was removed or is not connected.  Thats a very
  rare case.  Increasing the timeout to 60 seconds would make it less
  likely to have a false positive and have rc-sysinit start early.  (Ie,
  the case where a dhcp took 35 seconds).

  The user will only be punished by waiting an additional 30 seconds in
  the case that they have a  misconfigured or out of date
  /etc/network/interfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upstart 1.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  Date: Fri Sep  2 10:02:10 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to oneiric on 2010-11-15 (290 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions