Unfortunately, you aren't the first one to hit this problem and not the last one. So ideally we should find a way for the application to figure out those things before it hangs and tell the user how to fix them or at least print out the diagnosys information to help resolve the problem, without a user needed to contact this list.
I've emailed apr-dev to ask whether apr_uuid_get can be adjusted to have some sort of timeout mechanism.
So as Justin told me over apr-dev, the solution is to rebuild Apache with --with-devrandom=/dev/urandom - however, that is not secure for certain needs. Or setup EGD and use --with-egd.
Apache 2.1/apr-1.1 will have a self-contained PRNG generator built-in
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
