El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Hi, I listen into an UNIX socket but after stopping Unicorn the socket
is not removed. Is it the expected behavior?
Yes.
Otherwise it's subject to race conditions where the socket
owned by a new/replacement process gets its socket
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Otherwise it's subject to race conditions where the socket
owned by a new/replacement process gets its socket unlinked.
Currently Unicorn unlinks any existing socket on the FS before
attempting to bind to it for the following reasons:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Since there's absolutely no point in running Unicorn on port 80/443, you
should just avoid user switching entirely since it'll significantly
simplify your setup(s).
The problem are init scripts as they are executed by init process (as
El Lunes, 28 de Diciembre de 2009, Iñaki Baz Castillo escribió:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Since there's absolutely no point in running Unicorn on port 80/443, you
should just avoid user switching entirely since it'll significantly
simplify your setup(s).
The
Iñaki Baz Castillo i...@aliax.net wrote:
El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
Since there's absolutely no point in running Unicorn on port 80/443, you
should just avoid user switching entirely since it'll significantly
simplify your setup(s).
The problem are init
