> I mean i start uwsgi interactive (not daemon.. not tried daemon tough) > then send HUP with kill -HUP pid and after that ctrl-C doing reload > not exit. Is is expected?
Yes, SIGINT/SIGTERM/SIGQUIT/SIHUP blocks the delivery of other signals while running (without that you could end with orphaned workers, that will maintain a link to the socket, preventing new instances to spawn). Graceful reloads have a logic problem: a worker may be blocked in a request, preventing the procedure to end. For such reason there is a "mercy" timeout, after that the worker will be brutally killed: --reload-mercy 3 means, kill the worker if it does not end in 3 seconds With --touch-reload the graceful handling is not run by a signal handler, so it can get signals (like SIGINT) while running (this is not a problem, as touch-reload is not asynchronous like signals) > > 2012/3/15 Roberto De Ioris <[email protected]>: >> >>> Hello. >>> It is seems sigint handler is not restored after reload on hup but >>> works after touch-reload. >>> >> >> You mean, no way to sigint while graceul reloading or no more sigint >> handling after respawn ? The first is expected (to avoid races, and it >> is >> protected from infinite-wait via the no-mercy flags). The second case >> would be a serious problem. >> >> >> -- >> Roberto De Ioris >> http://unbit.it >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > > -- > -------------------------------------------- > Турнаев Евгений Викторович > +7 906 875 09 43 > -------------------------------------------- > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
