Sorry, but SIGHUP is also behaving like SIGINT and is not being graceful about working processes
On Fri, Apr 26, 2013 at 1:33 PM, Michael Hunley <[email protected]>wrote: > I am running uwsgi 1.9.7 on OsX 10.7. > > SIGINT and SIGQUIT are not doing a graceful shutdown. I am testing by > having a request do a looped sleep(1) in python 3.3 for 55 seconds. > SIGTSTP is gracefully "pausing" the worker processes and working > correctly, but if I issue either SIGINT or SIGQUIT to a master (zerg or > main) then the request is just killed, whether it has been sent SIGTSTP > previously or not. Am I doing something wrong? > > Also, SIGTSTP has a strange behavior if I have a thread sleeping. When I > first was testing with just a sleep(55) the SIGTSTP kicked the process out > of sleep and had it finish processing (I got the expected output, but it > did not wait the full time). That behavior could have some strange impacts > in certain situations. > > thanks > michael >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
