Hi,

On Tue, Jul 13, 2010 at 07:55:06AM +0200, nap wrote:
> We should have a better (and more multiplatform...) way to launch daemons :)

there are many ways to make services reliable and easy to launch/administrate.
The IMHO best approach is a superviser wich monitors the state, the PID
and more and does also start actions on specific events like i.e.
relaucnch a crashed service.

On Unix-style systems one of the best known and maybe the best supervising
software is the daemontools suite of Dan Bernstein. On the top level one
process is started which monitors the service supervisors. This process
is launched by init (with respawn). Therefore you have a "reliablity
chain". One of the big advantages of Bernstein's implementation is that
you can be sure that
1) the service will be restarted
2) and it will be only ONE instance started.

On many *ix systems and Linux distributions I've found many unreliable
startscripts like SysV-Scripts and "runscripts" (Gentoo). All of them
write a PID file and do not care anymore of the service any more after
starting. And many - MANY! - of these scripts sometimes start TWO
instances of the daemon causing trouble.

I suggest a implementation of the supervising concept. I don't how it can
be implemented on MS systems but I'm sure it must also be possible on
Windows to implement a reliability chain and a supervisor.

Frank

-- 

EDV Frank Bergmann                           Tel.     05221-9249753
LPIC-2 Linux Professional                    Fax      05221-9249754
Elverdisser Str. 25                          email    [email protected]
32052 Herford                                USt-IdNr DE237314606


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Shinken-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shinken-devel

Reply via email to