On 18/05/2010 12:00, George Kollias wrote: > Hello all, > > At events documentation (http://supervisord.org/events.html) paragraph > 1.7.3.4, it is said that "Other sample event listeners are present > within the supervisor package's |scripts| directory, including ones > which can monitor supervisor subprocesses and restart a process if it > is using "too much" memory". Unfortunately i found nothing relative to > memory monitoring there. Is there something somewhere else? If it > isn't, which is the recommended way to do it?
You could always use monit[1] to track the memory usage of the process(es), which can then use supervisorctl to restart them if they take over X memory. As a bonus, you can have monit keep an eye on the supervisord process, so if it ever goes down accidentally monit will bring it back up. [1] http://mmonit.com/monit/ -- *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
