There are deployments that do not use emperor mode but a single master process. The path to uwsgi tells witch “instance” is running so it is possible to accomplish everything else.
Even in emperor mode `quit` should mean shutdown them all gracefully. "Immediately kill the entire uwsgi stack" is not an option. Andriy Kornatskyy On Feb 16, 2014, at 10:29 AM, Mel Boyce <[email protected]> wrote: > On Sun, Feb 16, 2014, at 19:19, Andriy Kornatskyy wrote: >> The call is as follows: >> >> /usr/bin/uwsgi —quit >> >> That is. Nothing else. No pid, no fifo. >> >> Andriy Kornatskyy > > But how were you going to do it with a signal? > > And which uwsgi processes should gracefully quit with that command? > I run a cluster that supports about 10 different uwsgi applications via > emperor mode; what should that command do in that situation? > Also, shouldn't you use your init scripts to do that? > i.e., systemctl restart uwsgi@theapp or /etc/rc.d/rc.uwsgi-theapp.sh > restart or some such? > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
