clint at ubuntu.com
Tue Aug 16 17:46:42 UTC 2011
Excerpts from Steve Langasek's message of Tue Aug 16 10:18:34 -0700 2011:
> On Tue, Aug 16, 2011 at 09:43:07AM -0700, Clint Byrum wrote:
> > This mimics the old rc-sysinit which was based on two events virtually
> > guaranteed to happen. Then rc-sysinit has been changed to:
> > start on (filesystem and static-network-up) or started failsafe
> > And stat-network-up is an event that is emitted when all 'auto' interfaces
> > in /etc/network/interfaces are "up".
> > For non-servers, this means very little.. most of them only have lo in
> > /etc/network/interfacfes. For a server, it means we may delay entering
> > runlevel 2 by up to 30 seconds waiting for network interfaces to be
> > detected by the kernel and brought up. This gives a reasonable chance
> > that most multi-interface servers with services configured to start in
> > runlevel 2 bound to specific interfaces will have a successful boot.
> However, it also means that the services in runlevel 2 will attempt to start
> even if half the filesystem is missing. That could cause some
> unreliability, particularly in HA environments where an up-but-broken
> service may be worse than a down one?
I'm not sure I see how this can happen. failsafe only starts on filesystem
and net-device-up IFACE=lo.
More information about the upstart-devel