The following reply was made to PR general/1680; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Morgan Davis <[EMAIL PROTECTED]> Cc: Apache bugs database <[EMAIL PROTECTED]> Subject: Re: general/1680: Critically anomalous behavior when upgrading from 1.3a1 to 1.3b3 Date: Sat, 17 Jan 1998 16:54:14 -0700 (MST) On Sat, 17 Jan 1998, Morgan Davis wrote: > Marc Slemko writes: > > Are you _sure_ the child is a zombie? If the parent is dead, it shouldn't > > be. What releveant processes and info does a ps -axlw show? > > Yes, it was a zombie. Could not kill it with a -9, no matter what, > and it's parent PID was 1. But was its state 'Z'? A zombie shouldn't have a ppid of 1. > > When I was running the "virgin" 1.3b3, top indicated that most of the > httpds were in a "lockf" state. With the modified 1.3b3, most seem to > be in select, accept, or sbwait states, ala 1.3a1. Haven't seen a > lockf yet. Correct. lockf is what happens when it is doing the serialized accept() locking. > I'll let this modified 1.3b3 run for now until it acts up (hopefully > it won't). Are there any kinds of lines in the error log you're > particularly interested in? There's a lot of junk (File not found, > etc.) which is why we normally run it with error logging directed to > /dev/null. Not really. Note that in 1.3b2 and later you can use the LogLevel directive to specify what level of error messages you want to see in the error log.
