Todd Lipcon wrote:
Yep, this is a common problem. The fix that Brian outlined helps a lot, but
if you are *really* strapped for random bits, you'll still block. This is
because even if you've set the random source, it still uses the real
/dev/random to grab a seed for the prng, at least on my system.
Is there anyway to test/timeout for this on startup and respond?
At the very least, a new JIRA issue should be opened for this with the
stack trace and workaround, so that people have something to search on
