Il giorno 14/feb/2012, alle ore 11:22, Eugene Prokopiev ha scritto: >>> look at the emperor, by default it searches for single files, but could be >>> easily extended for other paradigms. >> >> Thanks, I'll see it > > How to stop uWSGI in emperor mode? I see it running again after kill > -INT/QUIT master pid: > > ... > SIGINT/SIGQUIT received...killing workers... > goodbye to uWSGI. > removed uwsgi instance /home/enp/uwsgi.ini > *** has_emperor mode detected (fd: 5) *** > [uWSGI] getting INI configuration from /home/enp/uwsgi.ini > … > Instances under the control of the emperor should never dies. If you want to fully stop an instance, simply remove/rename/move the instance config file in a way that the emperor rule will never match:
[uwsgi] emperor = /etc/uwsgi/enabled/*.ini move the ini file to /etc/uwsgi/disabled/ and you have done (or use symbolic-links, or some other rule, like enabling only the files starting with a _ and so on…) -- Roberto De Ioris http://unbit.it JID: [email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
