Il giorno 03/mar/2011, alle ore 11.41, Łukasz Wróblewski ha scritto: > I found even one case in which "vacuum" does not work according to my > thoughts. > > vacuum = 1 > > - Starts uWSGI "socket = a.sock" > - change in the ini file: "socket = b.sock" > - send a HUP signal > - after some time I finish the process uWSGI > > Socket a.sock never be erased. > It seems to me that when you create a new socket old should be removed when > the option vacuum is on. > >
That's a interesting (and very specific) case. The first purpose of graceful/brutal reload is leaving the socket opened to avoid clients receiving errors from the webserver. Changing socket open the gate to a really huge number of scenarios that are really hard to manage. Reloading is still a hard topic (i have seen a tweet where a user reported that uWSGI cannot self-heal from import error, and that is true), probably for 0.9.8 we should focus on this. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
