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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
