In article <1110471594.978818.191220@o13g2000cwo.googlegroups .com>,
"Morningwood" <adam.asay@gmail.com> wrote:

> Every couple of days a get a httpd process that just will not die
> normally, if I let it run it eventually eats up all time on the cpu.
>
> I've tweaked the tuneing parms in the httpd.conf, but I seem to be
> missing something.

Rather than focusing on tuning parameters, it would be better to try to
figure out what the particular process is doing when it spikes, then try
to prevent that from happening.

It's very likely that this sort of thing is due to a CGI script bug, NFS
error, database problem, or something like that. Just serving a static
HTML page should never cause this sort of CPU usage.

One way to try to figure this out is to install the server-status
handler. Then, find the PID of the bad process in "top", then switch
over to a browser and see what server-status says it's doing.

# Allow server status reports, with the URL of
http://servername/server-status
# Change the ".your_domain.com" to match your domain to enable.

<Location /server-status>
SetHandler server-status
order deny,allow
deny from all
allow from .your_domain.com
</Location>

--
Dan Wilga dwilga-MUNGE@mtholyoke.edu
** Remove the -MUNGE in my address to reply **