Yes that's what i am saying: after first hup ctrl-c also reloads. 2012/3/15 Roberto De Ioris <[email protected]>: > >> 2012/3/15 Roberto De Ioris <[email protected]>: >>> >>>> 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). >> >> I think we are talking about different situations. >> As i understand this: a signal is blocked in signal handler (to >> prevent reentering of handler). Thats ok, i am talking about after >> signal handler is done. i.e. uwsgi did execve on sighup and respawned >> worker.. after that i am doing ctrl+c and uwsgi is doing reload while >> after reload on touch ctrl+c works. Is this expected? >> >> > > You are saying a ctrl-c looks like sending a SIGHUP instead of a SIGINT ? > -- > 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
