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

[Leo Milano]

I will try to dig in a bit. My X clearly doesn't start until the penalty
120 secs expire, so I'd like to understand why, since for what you are
saying this shouldn't be the case (and there is, indeed, a kdm.conf in
/etc/init).

In the meantime: I use KDE, with KDM set to autologin to a user account.
In that user account, I run the script I show below (in
.kde/Autostart/). It basically runs an xterm, and then records the time
since boot started. It gives me a measure of the time from cold boot
into a usable desktop.

I will play a bit with lightdm, and will also try disabling autologin in
KDM.

Cheers
-- Leo

#!/bin/bash
#
# 2009, Leo Milano
#
# Credits: http://www.perlmonks.org/?node_id=11582
#          http://www.linuxscrew.com/2007/09/04/two-way-conversion-of-unix-time-seconds-since-1970-and-regular-time/
#

# Customize this if needed
log_file=~/boot_time.log

# A trick to make sure the script doesn't run this xterm in the background, 
# we want the window to popup before we go on with the script
# Choose one of the dummy commands below
dummy=`xterm -e echo hi`    

boot_time=`perl -ne 'print scalar $1 if /^btime (\d+)/' /proc/stat`
this_time=`date +%s`
let elapsed_time=this_time-boot_time

echo `date`. Boot Time [s]: ${elapsed_time} >> ${log_file}

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