Re: daemontools respin?

Charlie Brady wrote

> You do indeed have the same options. The run script for the dependent 
> daemon can employ just the same heuristics to determine when the daemon 
> that it depends on has fully started -  waiting for a PID-File to   
> appear somewhere, waiting for a socket to become available, etc.

You mean when B depends on A to be up, B may check availabily of A?

Of course you can do it this way, but then B may be forced to have
detailed knowledge about A's guts. Things become worse when B doesn't
require a certain daemon, but only a service in general, that does
something, e.g. any name server or any web server.

A clean way would be, if A can tell the supervisor: "I'm ready to
process requests", and then the supervisor starts all services that
depend on A.

Now go back to my recent mails, read again and then you might get how
the same may be achieved in a typical SysV setup (with self-daemonizing
daemons) quite easily.
-- 
Bernhard Graf