> On Wed, May 21, 2014 at 11:59 AM, Roberto De Ioris <[email protected]> > wrote: >> >> >> right, i suppose adding a check for them during the "fd 0" phase will be >> easy, i will give it a look > > > Great, thanks!
ths should address it (i did not tested it, so i will wait for your confirmation) https://github.com/unbit/uwsgi/commit/a0fafe78478ec32b5e6edfba77dfa06e93ac4070 > > While you're at it, a decent solution to the double socket creation might > be -- if socket is specified by a vassal, and emperor is in on-demand > mode, > then the emperor simply uses the path in the vassal's "socket = " > declaration instead of generating its own. > in <= 2.0.x the Emperor has no way to get informations from vassals configurations (this is why you need .socket files and similar). 2.1 (thanks to intellisurvey sponsorhip) introduced "attributes" to vassals, so a new set of configuration approaches will be available (and more important vassals can pass back informations to the Emperor) things like "spawn me in a new namespace, or spawn me in a docker container, or bind to 47 on-demand sockets" will be super-easy to implement -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
