On 22/10/2010 15:06, Jordi Funollet wrote: > On Friday 22 October 2010 10:05:13 Phillip Oldham wrote: >> We use supervisor in conjunction with Monit[1] which keeps an eye on >> resources (cpu/mem usage, disk usage, etc). Monit needs a PID file to be >> able to check how much resource a process is using, and then restart it >> (via supervisor) if it's being cheeky. > Phillip, > > Problably I'm going to ask something obvious, but if you are already using > 'monit', why do you need 'supervisord' too? Can't you just let 'monit' start > the daemon?
Monit is great as a back-up, but it's a little more "coarse" than supervisor. We would need to write init scripts for each program, whereas supervisor handles that much better than we can. We simply want to monitor cpu load for certain processes so that they restart if they misbehave. Currently supervisor can't do this. -- *Phillip B Oldham* ActivityHQ [email protected] <mailto:[email protected]> ------------------------------------------------------------------------ *Policies* This e-mail and its attachments are intended for the above named recipient(s) only and may be confidential. If they have come to you in error, please reply to this e-mail and highlight the error. No action should be taken regarding content, nor must you copy or show them to anyone. This e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium, and we have taken steps to ensure that this e-mail and attachments are free from any virus. We must advise that in keeping with good computing practice the recipient should ensure they are completely virus free, and that you understand and observe the lack of security when e-mailing us. ------------------------------------------------------------------------ _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
