From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: mongrel-unicorn@rubyforge.org
Subject: Re: Issue when sending USR2 too soon
Date: Sun, 17 Jan 2010 02:52:28 +0100 [thread overview]
Message-ID: <201001170252.28706.ibc@aliax.net> (raw)
In-Reply-To: <201001170244.55418.ibc@aliax.net>
El Domingo, 17 de Enero de 2010, Iñaki Baz Castillo escribió:
> Hi, I've realized that if I send USR2 very quicky to master process (each
> time to the new master process, of course) then sometimes Unicorn just
> dies totally and returns 0.
Sorry, I'm not sure if it returns 0 or not in such case since I'm doing the
check with a init script which performs the "reload" action by sending USR2 to
master process (which runs in background).
> Not sure, but I think that those times Unicorn receives the USR2 signal
> prior to load the code in which such signal is handled, could it be?
It makes sense since by default USR2 terminates a Ruby program.
What about if Unicorn very quicky prepares the trap for USR2 so in case it
receives it soon when starting it ignores it (and logs some warning)?
Does it make sense?
--
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:[~2010-01-17 1:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 1:44 Issue when sending USR2 too soon Iñaki Baz Castillo
2010-01-17 1:52 ` Iñaki Baz Castillo [this message]
2010-01-17 1:59 ` Iñaki Baz Castillo
2010-01-18 11:04 ` Eric Wong
2010-01-18 11:25 ` Iñaki Baz Castillo
2010-01-18 11:43 ` Eric Wong
2010-01-18 11:48 ` Iñaki Baz Castillo
2010-01-20 2:38 ` [PATCH] initialize signal handlers before writing pid file Eric Wong
2010-01-20 8:45 ` Iñaki Baz Castillo
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=201001170252.28706.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).