It will send the configured "stopsignal". The default is TERM. It will then wait the configured "stopwaitsecs" for the managed process to send a SIGCHLD response back to the parent. The default wait is 10 seconds. If supervisor does not receive SIGCHLD within that time limit, it will send a SIGKILL to the managed process. If that doesn't work, the process goes into a FAILED state, I believe.
On Oct 1, 2013, at 1:46 AM, Stuart Munro <[email protected]> wrote: > Hi All, > > We are running a lot of our processes under supervisord and think it's great! > One of our developers had a question in regards to stopping processes. > > When you send a "supervisorctl stop <process-name>" style command and the > process doesn't stop – does supervisord try again? Does it know that the last > command for that particular process was to "QUIT" the process and for some > unknown reason it didn't, and therefore Supervisord should try again until > the desired "stop" status is achieved? Or is it a fire and forget command > like normal init.d style scripts? > > Many thanks! > > _______________________________________________ > Supervisor-users mailing list > [email protected] > https://lists.supervisord.org/mailman/listinfo/supervisor-users
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Supervisor-users mailing list [email protected] https://lists.supervisord.org/mailman/listinfo/supervisor-users
