Behavior when init dies

I hear that if init dies, the zone will be rebooted.  Is
this true?  If
so, it seems heavy-handed.  Why not just log an error?


David
_______________________________________________
brandz-discuss mailing list
brandz-discussopensolaris.org

On Tue 08/22/06 at 14:02 PM, David.Bustossun.com
wrote:
> I hear that if init dies, the zone will be rebooted. 
Is this true?  If
> so, it seems heavy-handed.  Why not just log an error?

The Solaris kernel and init(1M) work together to provide a
clean warm
restart when it dies.  So when the Solaris init dies, the
kernel simply
restarts it and everything else in the zone keeps purring
along.

When the Linux init restarts, it goes through its entire
boot sequence
again.  This leads to oddities like having duplicate crond,
syslogd, and
other services.  In a perfect world, each of these services
would be smart
enough to detect that it already has an instance running,
and would simply
go away.  In this world, the failure mode is completely
undefined, and
varies from service to service.  We decided that a clean
restart was
preferable to leaving the zone in an unknown, untested,
unexpected, and
generally insane state.

This behavior is brand-dependent.  If another brand wants to
adopt the
standard Solaris behavior, it can easily do so.

Nils
_______________________________________________
brandz-discuss mailing list
brandz-discussopensolaris.org