Hi list,
Yes, Monit is the safest way: if liquidsoap crashes very badly, it
won't be able to perform any shutdown routines like sending mail
anyway. We use a solution like that for dolebrai.net -- except I
didn't know about monit so I wrote my own watchdog in shell script. I
start the monitoring process from the liquidsoap script, using
system("the script"). Juste one thing: add a little sleeping time
before probing the PID file, it's created a short while after the
execution of the configuration script.
Another solution, perhaps lighter but certainly weaker, is to use a
script and call it via system() and in an on_shutdown() callback. This
would still work most of the time, when liquidsoap crashes "cleanly",
i.e. when you see "Shutdown started!"
Have fun,
--
David
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
