To be a bit more precise my question is why when I kill the emperor I still have the 2 remaining processes. I was expecting to have 0.
> yml@toulouse:emperor-test$ cat uwsgi.pid > 8832 > yml@toulouse:emperor-test$ kill -9 `cat uwsgi.pid` > yml@toulouse:emperor-test$ ps -ef | grep uwsgi > yml 8833 1 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > yml 8836 8833 0 14:03 ? 00:00:00 uwsgi --emperor ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > yml 8872 13864 0 14:03 pts/6 00:00:00 tail -f uwsgi.log > yml 9252 13866 0 15:06 pts/7 00:00:00 grep --color=auto uwsgi > yml@toulouse:emperor-test$ Regards, --yml On Thu, Feb 3, 2011 at 3:50 PM, Roberto De Ioris <[email protected]> wrote: > > Il giorno 03/feb/2011, alle ore 15.14, Yann Malet ha scritto: > > > Roberto, > > > > I am looking a bit at the process running when I start and stop the > emperor. I am wondering why the emperor is letting 2 uwsgi processes behind. > > > > > > yml@toulouse:emperor-test$ ps -ef | grep uwsgi > > yml 8832 1 0 14:03 ? 00:00:00 uwsgi --emperor > ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log > --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > > yml 8833 8832 0 14:03 ? 00:00:00 uwsgi --emperor > ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log > --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > > yml 8834 8832 0 14:03 ? 00:00:00 uwsgi --xml > ./vassal-sites/site1/site1.xml > > yml 8835 8832 0 14:03 ? 00:00:00 uwsgi --xml > ./vassal-sites/site2/site2.xml > > yml 8836 8833 0 14:03 ? 00:00:00 uwsgi --emperor > ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log > --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > > yml 8837 8834 0 14:03 ? 00:00:00 uwsgi --xml > ./vassal-sites/site1/site1.xml > > yml 8838 8835 0 14:03 ? 00:00:00 uwsgi --xml > ./vassal-sites/site2/site2.xml > > yml 8872 13864 0 14:03 pts/6 00:00:00 tail -f uwsgi.log > > yml 9224 13866 0 15:03 pts/7 00:00:00 grep --color=auto uwsgi > > yml@toulouse:emperor-test$ cat uwsgi.pid > > 8832 > > yml@toulouse:emperor-test$ kill -9 `cat uwsgi.pid` > > yml@toulouse:emperor-test$ ps -ef | grep uwsgi > > yml 8833 1 0 14:03 ? 00:00:00 uwsgi --emperor > ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log > --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > > yml 8836 8833 0 14:03 ? 00:00:00 uwsgi --emperor > ./vassal-sites/*/*.xml --pidfile ./uwsgi.pid --daemon ./uwsgi.log > --fastrouter :3031 --fastrouter-use-cache --cache 100 --socket :3032 > > yml 8872 13864 0 14:03 pts/6 00:00:00 tail -f uwsgi.log > > yml 9252 13866 0 15:06 pts/7 00:00:00 grep --color=auto uwsgi > > yml@toulouse:emperor-test$ > > > > Regards, > > --yml > > > The first one is the emperor itself, the second one is the standard uWSGI > instance that receive requests for the caching subsystem > (but you can spawn all the workers you want in the emperor, for example i > am planning to export emperor data to allow > webapps to monitor and manage it) > > > The third one must be some kind of bug :) > > -- > Roberto De Ioris > http://unbit.it > > _______________________________________________ > 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
