* Re: [ANN] unicorn 4.8.0.pre1 prerelease gem
2013-12-09 9:54 7% [ANN] unicorn 4.8.0.pre1 prerelease gem Eric Wong
@ 2014-01-09 21:50 0% ` Eric Wong
0 siblings, 0 replies; 3+ results
From: Eric Wong @ 2014-01-09 21:50 UTC (permalink / raw)
To: mongrel-unicorn
Eric Wong <normalperson@yhbt.net> wrote:
> tests: fix SO_REUSEPORT tests for old Linux and non-Linux
> stream_input: avoid IO#close on client disconnect
> t0300: kill off stray processes in test
> always write PID file early for compatibility
> doc: clarify SIGNALS and reference init example
> rework master-to-worker signaling to use a pipe
Btw, has anybody tried this? I haven't noticed any issues, and I'm
thinking about releasing this as 4.8.0 as-is (with some minor doc
updates)
_______________________________________________
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
^ permalink raw reply [relevance 0%]
* [ANN] unicorn 4.8.0.pre1 prerelease gem
@ 2013-12-09 9:54 7% Eric Wong
2014-01-09 21:50 0% ` Eric Wong
0 siblings, 1 reply; 3+ results
From: Eric Wong @ 2013-12-09 9:54 UTC (permalink / raw)
To: mongrel-unicorn
Changes since 4.7.0:
Eric Wong (6):
tests: fix SO_REUSEPORT tests for old Linux and non-Linux
stream_input: avoid IO#close on client disconnect
t0300: kill off stray processes in test
always write PID file early for compatibility
doc: clarify SIGNALS and reference init example
rework master-to-worker signaling to use a pipe
gem install --pre unicorn
git://bogomips.org/unicorn
_______________________________________________
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
^ permalink raw reply [relevance 7%]
* Re: What does it mean for the unicorn process to be bound to a terminal?
@ 2013-11-26 19:21 6% ` Eric Wong
0 siblings, 0 replies; 3+ results
From: Eric Wong @ 2013-11-26 19:21 UTC (permalink / raw)
To: unicorn list; +Cc: Rodrigo Rosenfeld Rosas
Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:
> I see. If I understood correctly this only happens in foreground
> mode, so something like that would help me to understand the
> sentence:
> "...If your unicorn process is bound to an interactive terminal
> (running in the foreground), you can skip this step."
I used "not daemonized", since it's possible for a background process
to have a controlling terminal:
unicorn ... & # runs background, still attached to terminal
fg # foreground again
Pushed as fa17da92aa4e76d5fd63cb9b74d6884d611ec899
(also added a link to the init.sh example)
---------------------------8<----------------------------
Subject: [PATCH] doc: clarify SIGNALS and reference init example
"interactive terminal" needed clarification.
While we're at it, link to the init.sh example since it may
be shared with nginx.
Reported-by: Rodrigo Rosenfeld Rosas
ref: <5294E9D4.5030608@gmail.com>
---
SIGNALS | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/SIGNALS b/SIGNALS
index 8851775..48c651e 100644
--- a/SIGNALS
+++ b/SIGNALS
@@ -7,6 +7,9 @@ signal handling matches the behavior of {nginx}[http://nginx.net/] so it
should be possible to easily share process management scripts between
Unicorn and nginx.
+One example init script is distributed with unicorn:
+http://unicorn.bogomips.org/examples/init.sh
+
=== Master Process
* HUP - reloads config file and gracefully restart all workers.
@@ -101,8 +104,8 @@ The procedure is exactly like that of nginx:
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. Step 5 will be more difficult but
- you can also skip it if your process is not daemonized.
+ terminal (not daemonized), you can skip this step. Step 5 will be more
+ difficult but you can also skip it if your process is not daemonized.
4. You should now ensure that everything is running correctly with the
new workers as the old workers die off.
---------------------------8<----------------------------
> I believe it would help the documentation if you added a link to
> init.sh in the SIGNALS page:
>
> http://bogomips.org/unicorn.git/tree/examples/init.sh
> Anyway, even that script won't take care of making sure that the
> reload action will rollback in case of an unsuccessful deploy.
>
> I realize it's not easy to detect if the deploy was successful and
> that it's very application dependent, but some generic procedures
> would be helpful for a basic Rails application. Unfortunately I
> don't know what would be a good strategy, that's why I asked :P
Right. Different apps require different validation, especially
those intended for GUI web browsers.
> Thank you for explaining the interactive terminal binding question :)
No problem!
_______________________________________________
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
^ permalink raw reply related [relevance 6%]
Results 1-3 of 3 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2013-11-26 13:30 What does it mean for the unicorn process to be bound to a terminal? Rodrigo Rosenfeld Rosas
2013-11-26 18:04 ` Eric Wong
2013-11-26 18:35 ` Rodrigo Rosenfeld Rosas
2013-11-26 19:21 6% ` Eric Wong
2013-12-09 9:54 7% [ANN] unicorn 4.8.0.pre1 prerelease gem Eric Wong
2014-01-09 21:50 0% ` Eric Wong
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).