On Tue, Mar 06, 2007 at 03:09:51PM -0700, Tom Whitten wrote: > Nicolas Williams writes: > > Using the source I find this in $SRC/cmd/svc/startd/fork.c: > > ... > > Losing the running repository seems to be rather Bad, and causes sulogin > > to be started. I imagine that the only reasonable way to recover at > > that point is to reboot, so perhaps that's what svc.startd ought to do.
> From the sulogin the administrator can invoke > /lib/svc/bin/restore_repository to restore one of the backup repositories > or the seed repository. If the repository is corrupt/missing, rebooting > will merely get back to the sulogin prompt I believe. Looking at svc.configd source I see (I think) that CONFIGD_EXIT_DATABASE* errors can be produced when the volatile db is gone, not just the persistent repository. The way to recover from losing the volatile repository, I imagine, is to reboot. Restoring from a backup repository or from the seed repository would be needed only when the persistent repository is lost. Nico --
