That is a nice additiion, it removes some of the boilerplate code to set the name/socket in cache. Regards, --yml
On Fri, Feb 4, 2011 at 9:12 AM, Roberto De Ioris <[email protected]> wrote: > > Il giorno 03/feb/2011, alle ore 21.03, Roberto De Ioris ha scritto: > > > > >> 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. > > > > > > > > Ok, i have modified all the emperor stack in a way that every emperor > > child will die if the emperor dies. > > > > Let me know it it works flawlessly > > > > > Two other additions: > > --fastrouter-use-base <base> > > You can use this instead of caching, the hostname will be appended to > <base> > > Ex. > > --fastrouter-use-base /tmp/ > > will connect to /tmp/example.com > > > --fastrouter-use-pattern <pattern> > > The same concept but with magic substitution (only %s is supported mapped > to the hostname) > > Ex. > > --fastrouter-use-pattern /tmp/sockets/%s.sock > > > -- > 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
