On 1 May 1999 [EMAIL PROTECTED] wrote: > Somehow 242 seconds passed between the two time() calls... the parent does > nothing cpu intensive, so I doubt it's that. It's possible the guy's box > is swapping to hell... but we've got about a dozen similar reports.
Nope. In that case the load ought to rise, which it didnot. The problem was worked around by disabling keep-alives. > The reports are against 2.0.30, 2.0.32, and 2.0.33. After upgrading to kernel 2.0.36 and apache 1.3.4 I have been able to re-enable keepalives with no problems so far. > The short answer: kernel problem. Alan Cox hasn't heard of > this problem before, so it's probably an unknown problem. The short comment: Case appears solved by upgrading. /Ole
