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>
Subject: Re: Kernel.srand after_fork
Date: Fri, 28 Jan 2011 18:14:20 +0000	[thread overview]
Message-ID: <20110128181420.GA29648@dcvr.yhbt.net> (raw)
In-Reply-To: <20110128175111.GA18352@dcvr.yhbt.net>

Eric Wong <normalperson@yhbt.net> wrote:
> ghazel@gmail.com wrote:
> > So, calling Kernel.srand in after_fork will fix the 1.8 bug and the
> > 1.9.1 bug and work fine on 1.9.2?

Just reported the bug to ruby-core and pushed this out:

>From f4caf6b6bdea902abaadd3c04b2af94f056c4ff1 Mon Sep 17 00:00:00 2001
From: Eric Wong <normalperson@yhbt.net>
Date: Fri, 28 Jan 2011 18:11:26 +0000
Subject: [PATCH] KNOWN_ISSUES: document broken RNG+fork in newer Ruby 1.8

Reported by: ghazel@gmail.com

ref: <AANLkTimTpPATTpkoD2EYA2eM1+5OzCN=WxnCygQmJdhn@mail.gmail.com>
 KNOWN_ISSUES |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

index f218b83..259681d 100644
@@ -3,6 +3,11 @@
 Occasionally odd {issues}[link:ISSUES.html] arise without a transparent or
 acceptable solution.  Those issues are documented here.
+* Under some versions of Ruby 1.8, it is necessary to call +srand+ in an
+  after_fork hook to get correct random number generation.
+  See http://redmine.ruby-lang.org/issues/show/4338
 * For notes on sandboxing tools such as Bundler or Isolate,
   see the {Sandbox}[link:Sandbox.html] page.
Eric Wong
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

      reply	other threads:[~2011-01-28 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28  9:57 Kernel.srand after_fork ghazel
2011-01-28 10:26 ` Eric Wong
2011-01-28 10:57   ` ghazel
2011-01-28 17:51     ` Eric Wong
2011-01-28 18:14       ` Eric Wong [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=20110128181420.GA29648@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.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).