More on child-process just running (chewing CPU)

[Jim Jagielski <ji...@jaguNET.com>]

I've just found out another factoid about the "spinning child" syndrome that
I've been seeing... This is weird.

>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... 

Once again... the child process processes the request totally, including
making the "final" access_log entry, but the process keeps spinning,
chewing CPU, and reports itself as in the Write state... Any ideas? This
is baffling...
-- 
Jim Jagielski  << jim@jaguNET.com >>   |      "That's a Smith & Wesson,
  **  jaguNET Access Services  **      |       and you've had your six" 
      Email: info@jaguNET.com          |             - James Bond
++    http://www.jaguNET.com/         +++      Voice/Fax: 410-931-3157       ++