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

[Leo Milano]

Scott, is this how things are intended to work? My current understanding
is:


* "pre-start exec sleep N" means "wait up to N seconds for the preconditions to be satisfied". In this case, these are a network up and a fs up. I thought it meant "Wait at least N seconds", but I guess I was wrong.

* The current change makes the system to wait up to 120 seconds if the
network is not brought up according to /etc/network/interfaces

I think the latter is something that is not unlikely to happen for
people who have been using different network managers and upgrading to
new releases.

Why would we do this? Isn't it better to proceed with the boot up even
if the network is not fully up? Why is a network fully up a requirement
to run rc-sysinit.conf?

I would expect a flood of "my boot up takes 3 minutes" bug reports if
this released with a potential two minute lag.

Thanks!
Leo

-- 
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