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

Leo Milano lmilano at gmx.net
Thu Sep 8 04:11:19 UTC 2011


One more thought, just by looking at the script and the behaviour on my
system. The bug description states "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."

It seems to me that the sleep statement means that the bootup will take
AT LEAST 30 seconds, and a 120 sleep statement will ensure at least 120
seconds to boot up.

I am not an expert, so sorry if this silly, but isn't upstart all about
dependency based start up? It seems as if using sleep statements defeats
the whole purpose of the system?

-- 
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:
  Fix Released

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




More information about the foundations-bugs mailing list