From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: mongrel-unicorn@rubyforge.org
Subject: Re: Listening UNIX socket is not deleted when stopping Unicorn?
Date: Thu, 31 Dec 2009 15:57:57 +0100 [thread overview]
Message-ID: <200912311557.57499.ibc@aliax.net> (raw)
In-Reply-To: <20091228031546.GA4349@dcvr.yhbt.net>
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 unlinked.
>
> Currently Unicorn unlinks any existing socket on the FS before
> attempting to bind to it for the following reasons:
>
> * I consider this less error-prone, especially when people aren't
> storing sockets in a directory that's cleared on reboots (like /tmp).
>
> * This can also be desirable behavior since it can be used to do
> transparent upgrades/binary replacements in cases where it's less
> convenient to use USR2+QUIT, if you're switching between Ruby
> installations for example.
Hi, just a question:
Then is it totaly safe to delete the socket before starting Unicorn?
I expect the answer is yes as Unicorn does it.
Thanks.
--
Iñaki Baz Castillo <ibc@aliax.net>
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2009-12-31 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 0:37 Listening UNIX socket is not deleted when stopping Unicorn? Iñaki Baz Castillo
2009-12-28 3:15 ` Eric Wong
2009-12-28 10:39 ` Iñaki Baz Castillo
2009-12-28 10:48 ` Iñaki Baz Castillo
2009-12-28 11:51 ` Iñaki Baz Castillo
2009-12-28 19:06 ` Eric Wong
2009-12-31 14:57 ` Iñaki Baz Castillo [this message]
2009-12-31 19:42 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200912311557.57499.ibc@aliax.net \
--to=ibc@aliax.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).