Nicolas Williams writes:
[SNIP]
>
> 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
> --
Nico,
Sorry for the delay in getting back to you.
You are correct. svc.configd will exit with an error if there are problems
with either the persistent or non-persistent database. When svc.startd
sees that configd exited with a database error, it will invoke sulogin.
You are also correct that the way to recover from loosing the
non-persistent repository is to reboot. From looking at the code, it looks
like svc.configd writes out the name of the repository file that caused the
problem in its error messages. So from the file name, it should be possible
to determine if it was the persistent or non-persistent repository that
caused svc.configd to exit.
tom
