> Can you tell me more about the bug you had? What does a "socket options > issue" mean? Do you know what ac_cv_o_nonblock_inherited is doing when > it gets set?
What I remember is this: Deep inside APR, the socket module attempts to cache socket option information (such as blocking flags) in order to reduce the number of system calls made. On the OpenBSD platform, the state of a socket's non blocking flag was different from the initial state assumed (and cached) by APR. Because the initial cached copy was wrong, attempts to set the flag to the correct value would fail to cause an actual system call ... therefore the blocking state never actually changed. TTUL Ken -- MailChannels: Assured Messaging -- Eliminate Critical False Positives http://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 Sent by MailChannels: http://www.mailchannels.com
