Buck Evan:
For example, I'd like to encode the fact that I don't expect service A to be
able to come up before service B.
In nosh, the filesystem is the database. This is an ordering, not a
dependency. One can separately encode in nosh (a) that start of service
B will cause the start of
Avery Payne:
There's already a project for adding definitions for various daemons.
http://bitbucket.org/avery_payne/supervision-scripts
There are even more than that. I mentioned back in January that the
nosh Guide chapter on creating service bundles has pointers to the run
file collections
(Gah, idiotically neglected the proper destination.)
It seems to me that the domineering philosophy for fault tolerance is,
indeed, to let it crash and let the individual state management of
services coupled with any existing supervisor trees and priority
rankings to do their work.
From my
