Upstart plans

[Steve Langasek]

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?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/upstart-devel/attachments/20110816/278f3f44/attachment.pgp>