Is it possible there is a problem with this change? Since I upgraded to 3.6.0 I have encountered two collisions on ActiveSupport::SecureRandom.hex(64), which seems very unlikely, since it has never happened in the history of my app otherwise.
-Greg On Wednesday, April 20, 2011, Eric Wong <[email protected]> wrote: > Changes: > > Mainly small fixes, improvements, and workarounds for fork() issues > with pseudo-random number generators shipped with Ruby (Kernel#rand, > OpenSSL::Random (used by SecureRandom and also by Rails). > > The PRNG issues are documented in depth here (and links to Ruby Redmine): > > http://bogomips.org/unicorn.git/commit?id=1107ede7 > http://bogomips.org/unicorn.git/commit?id=b3241621 > > If you're too lazy to upgrade, you can just do this in your after_fork > hooks: > > after_fork do |server,worker| > tmp = srand > OpenSSL::Random.seed(tmp.to_s) if defined?(OpenSSL::Random) > end > > There are also small log reopening (SIGUSR1) improvements: > > * relative paths may also be reopened, there's a small chance this > will break with a handful of setups, but unlikely. This should > make configuration easier especially since the "working_directory" > configurator directive exists. Brought up by Matthew Kocher: > http://thread.gmane.org/gmane.comp.lang.ruby.unicorn.general/900 > > * workers will just die (and restart) if log reopening fails for > any reason (including user error). This is to workaround the issue > reported by Emmanuel Gomez: > http://thread.gmane.org/gmane.comp.lang.ruby.unicorn.general/906 > > > * http://unicorn.bogomips.org/ > * [email protected] > * git://bogomips.org/unicorn.git > > -- > Eric Wong > _______________________________________________ > Unicorn mailing list - [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-unicorn > Do not quote signatures (like this one) or top post when replying > _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
