I use supervisord to create and manage a FastCGI application that I write in C for target Linux. I have a signal handler that gracefully exits my application when I receive SIGINT. I checked that the signal handler works as desired by running the application in the terminal window and releasing Ctrl-C to exit.
When issuing the shutdown command to the supervisor (via supervisorctl), it seems that the supervisor cannot force the application to exit without calling SIGKILL:
2010-08-20 10:02:49,661 INFO waiting for cse to die
2010-08-20 10:02:52,665 INFO waiting for cse to die
2010-08-20 10:02:55,669 INFO waiting for cse to die
2010-08-20 10:02:58,672 INFO waiting for cse to die
2010-08-20 10:02:59,673 WARN killing 'cse' (2031) with SIGKILL
2010-08-20 10:02:59,674 INFO stopped: cse (terminated by SIGKILL)
I have the following in supervisord.conf
stopsignal=INT
This is my assumption that supervisord issues "stopignal" when the shutdown command is called, so I accept INFO instructions as an indication that my application does not respond to the SIGINT issued by the supervisor.
, ?