> From: Bill Stoddard [mailto:[EMAIL PROTECTED]]
> The only way that I can see Apache 1.3 getting stuck on keepalive > reads is: > 1. storage overlay that whacked the timeout value to some BIG > NUMBER (unlikely I think) > 2. signals are not being delivered either because of a bug in the > OS or because some > errant module has blocked signals. > 3. Some module has started one or more additional threads w/o > blocking signals in the new > thread. The new thread could be catching the keep-alive timeout > signal rather than the > thread blocked on the read. 2 or 3 sound right to me. It is amazing the variety of wacky libraries that Apache winds up sharing process space with. Joshua.
