On Nov 16, 2007 4:32 PM, David Jones <[EMAIL PROTECTED]> wrote: > A read on /dev/random (and /dev/urandom) returns a 0 instead of a -1 to > indicate an error on zOS levels 1.6 and prior. > This puts apr/misc/unix/rand.c and therefore /test/testrandom into an > infinite loop. > For zOS 1.7 and above, a read returns the expected number of bytes read, or > a -1 if there's an error (ex. crypto hardware (ICSF) is not usable). > > Add to the config checks for random a zOS level check. For zOS 1.7 and above ...
Please check the patch I just committed to apr trunk (http://svn.apache.org/viewvc?view=rev&revision=596126) The patch you submitted had some issues. In the technical realm, I moved the check for old z/OS to a different place so that it could trap --with-devrandom, default, and --with-devrandom=/dev/random invocations. The explanation message was moved to the common AC_MSG_RESULT() message to preserve the pattern Checking for foo... what-happened
