unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Brian P O'Rourke <bpo@somnambulance.net>
Subject: Re: sigwinch and screen
Date: Wed, 14 Sep 2011 17:32:13 +0000	[thread overview]
Message-ID: <20110914173213.GA31955@dcvr.yhbt.net> (raw)
In-Reply-To: <CAOowiR3XgNfTs9N7TskECHGHxra4A=gF-bk4XBxskkCzJxc7tA@mail.gmail.com>

Brian P O'Rourke <bpo@somnambulance.net> wrote:
> (my apologies if this gets posted twice - don't think my earlier mail
> went through)

I've noticed rubyforge has occasional slowness :<   It uses Postgrey so
first time posters could be delayed...

> I'm running unicorn within screen and have run into some trouble.
> Unicorn tries to ignore sigwinch when it's not daemonized.
> Unfortunately the check for daemonization fails when unicorn is exec'd
> from a process that already has a pgrp.
> 
> You can simulate this problem from *within* a screen session with
> something like this:
> 
>     screen sleep 5 && screen bundle exec unicorn -c unicorn.conf config.ru

So, start "screen", get a terminal + shell, /then/ type the above?

> sigwinch will be sent to the second screen session the first time you
> change to it. This doesn't happen unless you launch at least two
> screens in rapid succession, for reasons that escape me so far -
> haven't dug into that part much yet.

I haven't been able to reproduce it on my end.
It could be system-dependent (terminals are often wonky/inconsistent).

> It seems to me that this is a problem, and is occurring because
> Unicorn's check for daemonization is "is init my parent or is my group
> different from my pid?", which isn't necessarily the same as checking
> whether daemonization has happened.

Agreed.  Regardless of what the problem is, I like your check based on
RACKUP[:daemonized].  It's much more readable and obvious :)

> Here is the patch I would like to see applied:

I'll apply it.   Is there a commit message you'd like to use?
(Otherwise I'll just edit something based on your email)

Thanks!

> --- a/lib/unicorn/http_server.rb
> +++ b/lib/unicorn/http_server.rb
> @@ -282,7 +282,7 @@ class Unicorn::HttpServer
>        when :USR2 # exec binary, stay alive in case something went wrong
>          reexec
>        when :WINCH
> -        if Process.ppid == 1 || Process.getpgrp != $$
> +        if Unicorn::Configurator::RACKUP[:daemonized]
>            respawn = false
>            logger.info "gracefully stopping all workers"
>            kill_each_worker(:QUIT)
-- 
Eric Wong
_______________________________________________
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

  reply	other threads:[~2011-09-14 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOowiR0YXF6TAY2_Sv0KYfr0UL-VCAX=KX8OO_-DnOLG-hDbSA@mail.gmail.com>
2011-09-14 14:29 ` sigwinch and screen Brian P O'Rourke
2011-09-14 17:32   ` Eric Wong [this message]
2011-09-15  0:44     ` Brian P O'Rourke
2011-09-15  0:54       ` 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=20110914173213.GA31955@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=bpo@somnambulance.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).