On Fri, Mar 27, 2009 at 10:52 AM, Chris McDonough <[email protected]> wrote:
> Harald Friessnegger wrote: > > is there a way, or is there a plan to be able to monitor the memory usage > of a > > process and all it's subprocesses using memmon? > > Supervisor itself can't manage any process that it doesn't itself start. > This > is because supervisor relies on signals sent by its children in order to > turn > these into events that are processed and notify event listeners. These > same > signals are not sent to supervisor by children of processes not themselves > started by supervisor. This won't change in any near future unless someone > knows some way around it (maybe via some process group thing or something). > I > certainly don't know how to make it happen portably. > It's not portable but it seems like the alternative to using SIGCHILD is to integrate with a kernel module and get information about the process that way. Looks like god (http://god.rubyforge.org/) takes that approach. "God currently only works on *Linux (kernel 2.6.15+), BSD,* and *Darwin*systems. No support for Windows is planned. Event based conditions on Linux systems require the cn (connector) kernel module loaded or compiled in to the kernel and god must be run as root." > > It can of course event listeners can do *anything* when they subscribe to > TICK > events. So what you describe (summing up process memory usage of all > processes > that have a ppid of some process managed by supervisor) could be done. You > could probably change memmon to do so; I'm not sure whether it can be done > completely portably but probably so. > > - C > > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
