This is in addition to killasgroup. Killasgroup doesn't work for this situation b/c the parent process exits after receiving SIGTERM. Supervisor never sends SIGKILL b/c the parent is dead. This leaves the child orphaned.
On Fri, Mar 30, 2012 at 2:59 PM, Ales Zoulek <[email protected]> wrote: > Hey, > > we already have that [1] and it's called killasgroup :) > > 1] > https://github.com/Supervisor/supervisor/blob/master/supervisor/process.py#L354 > > > Cheers, Ales > > ------------------------------------------------------ > Ales Zoulek > +420 604 332 515 > Jabber: [email protected] > ------------------------------------------------------ > > > On Fri, Mar 30, 2012 at 8:40 PM, Roger Hoover <[email protected]>wrote: > >> Hi, >> >> Any objections to a "stopasgroup" option? >> >> I've run into a case where I want to run Flask in debug mode under >> supervisord in development and the parent Flask process doesn't propagate >> the SIGTERM or SIGINT signals to it's child, >> leaving it orphaned. This doesn't happen on the command line b/c the >> shell sends SIGINT to the entire foreground process group. >> >> For cases like this, it would be useful to be able to set an option, >> called stopasgroup, that sends the stop signal to the whole process group. >> >> Cheers, >> >> Roger >> >> >> _______________________________________________ >> 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
