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

[Scott Moser]

Public bug reported:

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)

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug oneiric running-unity

-- 
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 “upstart” package in Ubuntu:
  New

Bug description:
  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/+source/upstart/+bug/839595/+subscriptions