What does it mean for the unicorn process to be bound to a terminal?

From: Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com>
To: mongrel-unicorn@rubyforge.org
Subject: What does it mean for the unicorn process to be bound to a terminal?
Date: Tue, 26 Nov 2013 11:30:49 -0200	[thread overview]
Message-ID: <5294A289.1020300@gmail.com> (raw)

For a long time I struggle to understand this part:

http://unicorn.bogomips.org/SIGNALS.html

"3. You can now send WINCH to the old master process so only the new 
workers serve requests. If your unicorn process is bound to an 
interactive terminal, you can skip this step."

I asked a teammate and he didn't understand this part either, so maybe 
it's confusing for other people too.

Would you mind to clarify what you mean by that?

Also, a section with suggestions on how to properly automate a 
deployment with no downtime would be helpful.

What I see is that most recipes, like the ones I've seen for Capistrano 
for example, will simply send a QUIT after USR2 to the old master 
without actually checking if the deploy was successful and won't use the 
WINCH and HUP signals to deal with health checking...

Cheers,
Rodrigo.

_______________________________________________
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