[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Leo Milano
lmilano at gmx.net
Thu Sep 8 02:23:22 UTC 2011
Oh yes, changing that value in failsafe.conf brings back the old boot times:
tried setting to 12 and then 1, and it definitely fixed things: ( I added the //comments )
Wed Sep 7 17:13:34 PDT 2011. Boot Time [s]: 156 // Sleep 120
Wed Sep 7 18:59:59 PDT 2011. Boot Time [s]: 51 // Sleep 12
Wed Sep 7 19:04:28 PDT 2011. Boot Time [s]: 48 // Sleep 12
Wed Sep 7 19:10:36 PDT 2011. Boot Time [s]: 37 // Sleep 1
This is how it looks now:
#################
santisofi at minime:~$ cat /etc/init/failsafe.conf
# failsafe
description "Failsafe Boot Delay"
author "Clint Byrum <clint at ubuntu.com>"
start on filesystem and net-device-up IFACE=lo
stop on runlevel
pre-start exec sleep 1
#################
So, it looks like, around Sept 3, something changed with an update, and
I started going to sleep for 30 secs (so boot times went around 30 sec
longer). Then, this recent change to 120 added extra 90 secs. I looked
around in dmesg and didn't find anything obvious. I will attach it
shortly, regardless.
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
More information about the foundations-bugs
mailing list