Ken,
Thanks for the explanation. For better or worse, after a rebuild of
mod_perl all of my tests are now working. I don't know what I changed
but I've logged out and back onto the system and rebuilt from scratch.
Everything is running perfectly which is great. Now to see if my
segfault with Image
> 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 orde
On Thu, Jun 02, 2005 at 09:37:51AM -0700, Ken Simpson wrote:
> It _may_ (just because I have a gut feeling, not because of actual
> consideration) be a socket options issue that may be related to your
> platform. I had a very similar problem with OpenBSD last summer
> wherein the socket blocking st
It _may_ (just because I have a gut feeling, not because of actual
consideration) be a socket options issue that may be related to your
platform. I had a very similar problem with OpenBSD last summer
wherein the socket blocking status could not be changed. The fix was a
very simple change to the co
-8<-- Start Bug Report 8<--
1. Problem Description:
Following on the heels of my previous post to Stas regarding an old
thread, I've another test failure report. This one is for
t/protocol/pseudo_http.pm. It is failing because the connection to the
server is
