From: rst@ai.mit.edu (Robert S. Thau)
Date: Mon, 1 Apr 1996 20:32:48 -0500
Message-Id: <199604020132.UAA07438@volterra.ai.mit.edu>
To: new-httpd@hyperreal.com
Subject: Re:  More on child-process just running (chewing CPU)
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com
Status: O

  >From what I can see, the request is processed, it's "written" (outputed)
  to the client (correctly) and it's even logged (!!)... it's just, for
  some reason, the socket isn't being closed or something... 

What this means is that it's looping trying to flush its buffers before
closing the socket to the client and moving on, but after having logged
the transaction (and very possibly after a timeout).

Have you managed to get a stack backtrace of a spinning process?  (If
gdb on your system won't do "attach", you may still be able to send a
spinning process a "kill -SIGBUS", and give it a core dump to work
with).

rst