On Sun, Feb 16, 2014, at 19:39, Andriy Kornatskyy wrote: > 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
I run quite a few of those and I just use systemctl to manage that situation (from scripts to reload the applications via a REST API). In emperor mode, I use the old school machanism of touching the application ini files to reload gracefully. I guess I don't understand your motivation given that the methods supported by uWSGI right now appear to me to be simple and predictable - i.e., I don't have to guess as to what will happen if I use either touch, the master fifo, my init system, or signals. _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
