[Developers, this is regarding the client's tendency to wait for a
long time on systems where APR is configured to use /dev/random
instead of /dev/urandom, but there isn't enough random data for what
Subversion requests at a given moment.]
Pete Gonzalez <pgonzalez@bluel.com> writes:
> At 01:02 PM 2/16/2005, kfogel@collab.net wrote:
> >But, what if Subversion is sharing APR with other applications? Can
> >Subversion just do whatever it wants with APR configuration?
> >Sometimes Subversion is linking against an existing APR, not building
> >its own.
> >(Of course, we could at least change our install instructions to
> >stipulate that if one *is* building APR just for Subversion, one
> >should configure with "--with-devrandom=/dev/urandom".)
>
> This is an interesting point. IMO the ideal solution would be to
> convince the APR people to fix their library, but if memory serves,
> the problem is from apr_generate_random_bytes() and only affects
> Subversion via the getuuid.c file. If you look at the source code,
> writing a custom replacement for apr_uuid_get() is trivially easy and
> you could probably improve the implementation.
Or we could finally become multi-threaded, and spawn one thread to get
the random bytes from APR, while another one tries the custom
implementation if the first takes too long...
Mostly kidding there, but yes, you have a point :-).
Developers, would we want a patch as suggested by Pete Gonzalez above?
I'm inclined to say "yes", but would like others' thoughts.
The problem is real. I've frustratingly experienced this lockup
myself, in fact.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 16 23:23:02 2005