On Tue, Jan 10, 2017 at 9:45 PM, Dennis Clarke <dcla...@blastwave.org> wrote: > On 01/10/2017 06:03 PM, Yann Ylavic wrote: >> >> On Tue, Jan 10, 2017 at 6:50 PM, Dennis Clarke <dcla...@blastwave.org> >> wrote: >>>> >>>> >>>> Could you strace (truss?) a simple main() that calls rand() to confirm? >>> >>> >>> Even better, Dtrace. >>> >>> Regardless I am juggling a few things and will get right on this. >> >> >> Thanks for investigating. >> >> Also, when at this, could you please provide the value of DEV_RANDOM >> in "include/arch/unix/apr_private.h" (i.e. /dev/random or >> /dev/urandom) for your ./configure'd tests? > > Well let's just come to a full stop here. :-\ > > Sure enough if we switch over to /dev/urandom then the tests run very > neatly and at good speed. See log attached. > > So .. blocking source of random data has to be the issue.
Thanks Dennis for the follow up. /dev/urandom is the default (if existing), so if you don't ./configure --with-devrandom explicitly it should work too.
