On Wed, Nov 15, 2006 at 12:10:30PM +0100, [EMAIL PROTECTED] wrote: > > >I think we first need to define what state "up" actually is. Is it the > >kernel booted ? Is it the root file system mounted ? Is it we reached > >milestone all ? Is it we reached milestone all with no services in > >maintenance ? Is it no services in maintenance that weren't on the last > > boot ? > > I think that's fairly simple: "up is the state when the milestone we > are booting to has been actually reached". > > What should SMF do when it finds that it cannot reach that milestone?
Another question might be: how do I fix it when it's broken?
> Harder is:
>
> What is the system does not come up quickly enough?
> What if the system hangs before SMF is even starts?
> What if the system panics during boot or shortly after we
> reach our desired milestone?
>
> And then, of course, "define shortly and quickly".
Such definitions to consider net and SAN booting.
Personally I think if a system is hosed then the best way to fail-safe
is to either panic or drop to single-user rather than trying to be
clever and booting some other kernel.
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
pgpT7hoII5pKc.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
