Looking at things again, perhaps before injesting enough caffeine, it looks like there are other bogosities w.r.t. timeouts that perhaps hid the bug from me for my particular testcase. I see various places where we think that sock->timeout != 0 means there is a timeout in place, when a check via apr_is_option_set(sock->netmask, APR_SO_TIMEOUT) is the proper thing to do.
Ok, I see.. yeah the only code I really focused on was that one function.
I now see that your patch needs to be committed, but for the short term I'd like to explore some other bogosities.
Thanks for hanging in there!
Ok, I've recompiled and tested with the new changes and things seem to be working fine (for the past couple hours). I'll drop a line if anything surfaces later. Hey, and thanks for the timely resolution.
-- jacob lewallen [EMAIL PROTECTED]
