From: Eric Wong <firstname.lastname@example.org>
To: unicorn list <email@example.com>
Subject: Re: Kernel.srand after_fork
Date: Fri, 28 Jan 2011 10:26:49 +0000 [thread overview]
Message-ID: <20110128102649.GB25922@dcvr.yhbt.net> (raw)
> We recently noticed random numbers from the Unicorn workers were
> turning up lots of duplicates across requests. Is it possible that the
> random seed generated when the ruby interpreter starts is duplicated
> when the workers are forked, and not re-seeded after fork?
> If so, should I call Kernel.srand in after_fork, or is this something
> which should be added to Unicorn?
It looks like a 1.8 bug, which version of Ruby are you running? Ruby
1.9.1 actually had a bug where it was reseeded improperly and led to
segfaults (see KNOWN_ISSUES). 1.9.2 is fine afaik.
Unicorn mailing list - firstname.lastname@example.org
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-01-28 10:31 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 [this message]
2011-01-28 10:57 ` ghazel
2011-01-28 17:51 ` Eric Wong
2011-01-28 18:14 ` Eric Wong
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 \
* 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).