> I tried with the github source as you said only for socketio > serve_forever: > > attach-daemon2 = cmd=/path/to/python > /path/to/runserver.py,stopsignal=SIGINT,reloadsignal=SIGHUP > > http://pastebin.com/TkqBSiyE > > I wasn't sure for the signal names but these were the closest options I > gave. It didn't show any progress and "reload" started to kill daemon > brutally instead of gracefully. >
--attach-daemon2 takes signal numbers (9 for KILL and so on) > R > > For stopping and restarting, nothing seems changed: > Wed Jan 15 14:40:26 2014 - [uwsgi-daemons] spawning "/path/to/python > /path/to/runserver.py" (uid: 1000 gid: 1000) > Server running on port :9100. Ctrl+C to quit > == stop command here == > Wed Jan 15 14:40:43 2014 - uWSGI worker 4 screams: UAAAAAAH my master > disconnected: i will kill myself !!! > Wed Jan 15 14:40:43 2014 - uWSGI worker 2 screams: UAAAAAAH my master > disconnected: i will kill myself !!! > Wed Jan 15 14:40:43 2014 - uWSGI worker 1 screams: UAAAAAAH my master > disconnected: i will kill myself !!! > Wed Jan 15 14:40:43 2014 - uWSGI worker 3 screams: UAAAAAAH my master > disconnected: i will kill myself !!! > > and the process remains zombie.. By the way, this master app is run by the > emperor if it helps. wait, something here is wrong, are you sending control-c from the keyboard ? it looks like your master is catching it as well as the daemon (and in addition to this the master is abruptuly killed) Can you manually send SIGINT only to the master ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
