unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public@bogomips.org, Jesse Storimer <jstorimer@gmail.com>
Subject: Re: Bug, Unicorn can drop signals in extreme conditions
Date: Wed, 18 Feb 2015 17:27:39 +0000 (GMT)	[thread overview]
Message-ID: <fc17b4534812.54e4cb8b@langara.bc.ca> (raw)
In-Reply-To: <20150218091517.GA21920@dcvr.yhbt.net>


Okay, my apologies, I misunderstood the signal handling code.  I
thought you were doing something like
self_writer.write_nonblock(signal) instead.  This is what I thought of
initially because I was still thinking in the context of C (where
signals are not deferred and allocating new space on a queue in a
signal handler would be unsafe) instead of in the context of Ruby
where Ruby's signals are deferred.  Incidentally, MRI's signal handler
implementation in signal.c appears to be broken in several ways but
that is a separate topic for a separate place.

Thank you,
Steven Stewart-Gallus

      reply	other threads:[~2015-02-18 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  2:19 Bug, Unicorn can drop signals in extreme conditions Steven Stewart-Gallus
2015-02-18  9:15 ` Eric Wong
2015-02-18 17:27   ` Steven Stewart-Gallus [this message]

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:

  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=fc17b4534812.54e4cb8b@langara.bc.ca \
    --to=sstewartgallus00@mylangara.bc.ca \
    --cc=e@80x24.org \
    --cc=jstorimer@gmail.com \
    --cc=unicorn-public@bogomips.org \


* 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


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).