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

[Clint Byrum]

Excerpts from Leo Milano's message of Thu Sep 08 19:17:14 UTC 2011:
> @ Scott: thanks for the detailed response. It all makes sense now. I am
> guessing perhaps wicd wrote that entry in my interfaces  file. I haven't
> edited this file by hand.
> 
> @ Clint: yes, I think it makes sense to add this to the release notes.
> Thanks for updating the description. It seems like this is a reasonable
> approach for now.
> 
> Longer term, I think the start system needs more granularity. Ideally,
> if the network is still not up, most services (except for things like
> ntp, firewalls, etc) should start anyway. The user should still be able
> to get X up and running, and be able to login. But the current structure
> of one upstart hook to all sysvinit services won't allow for that.
>

Anything that a user depends on having before X is up should be an
upstart job and have a very granular start up. This change should only
affect general network services.

If you look, X should already be independent of this delay. Here is the
start condition for lightdm:

start on (filesystem
          and started dbus
          and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
               or stopped udevtrigger))

All of that can happen before runlevel 2 is emitted (which is all that is
actually blocked). I'm curious what your script measures as "boot time",
in the past, "able to log in" was used as the measurement.

> Thank you for the great work, and I hope this little extra bit of info
> benefits other users.

Leo, thanks for the heads up, I appreciate your testing and the feedback,
keep it coming!

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