Hey,

Came up against another curious problem today.

Supervisor seems to not always kill uwsgi correctly, and sometimes can end
up with workers still listening on the unix socket.

Although the answer is ultimately to kill the uwsgi processes, this is not
something which can always be detected or automated.

Is it possible to force uWSGI to create an exclusive lock on a unix socket,
and if it encounters another uWSGI master instance, it will refuse to
listen on the socket and die?

I saw 'no-orphans', but this would only work if the master instance was
dead (which it doesn't appear to be).

Thanks

Cal
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to