> On Wed, May 21, 2014 at 11:33 AM, Roberto De Ioris <[email protected]> > wrote: > >> Hi Jason, could it be your case ? : >> >> https://github.com/unbit/uwsgi/issues/608 >> >> basically 2.0.4 introduce true graceful reload for on-demand socket, but >> if you define a socket directive in the vassal file too, it will telete >> the original socket (sort of race condition). You should note (even in >> 2.0.3) that your vassal initialize the socket twice (which is wrong) >> >> > The problem with the solution there is that chown-socket and chmod-socket > no longer have any effect. This is problematic from a security > perspective. > _______________________________________________ >
Double-initializing the socket still seems wrong to me (even if it looks like it does not cause unexpected behaviours). The (current) best solution would be using hooks (in the vassal): hook-asap = chmod:<file> <mode> hook-asap = chown:<file> <uid> <gid> what we could add (to bring back the unexpected old feature) is a way for telling the emperor to close the socket and disable graceful reloading (but i find hooks a more versatile way) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
