cool that's interesting i'll check it outOn 10/19/05, Joshua Slive <[EMAIL PROTECTED]> wrote:
On 10/19/05, Joe A <[EMAIL PROTECTED]> wrote:> oh ok, i guess you are talking about using top to find an httpd process with> high cpu? then how do i attach a debugger to it?
gdb /path/to/httpdattach pidwhe
On 10/19/05, Joe A <[EMAIL PROTECTED]> wrote:
> oh ok, i guess you are talking about using top to find an httpd process with
> high cpu? then how do i attach a debugger to it?
gdb /path/to/httpd
attach pid
where
(replace pid with the process id obtained from top)
http://httpd.apache.org/dev/debug
oh ok, i guess you are talking about using top to find an httpd process with high cpu? then how do i attach a debugger to it?On 10/19/05, Joshua Slive <
[EMAIL PROTECTED]> wrote:On 10/19/05, Joe A <
[EMAIL PROTECTED]> wrote:> joshua,>> what do u mean by "shows a process on cpu"?Something with high
On 10/19/05, Joe A <[EMAIL PROTECTED]> wrote:
> joshua,
>
> what do u mean by "shows a process on cpu"?
Something with high cpu usage.
Joshua.
-
The official User-To-User support forum of the Apache HTTP Server Project.
See htt
joshua,
what do u mean by "shows a process on cpu"?On 10/19/05, Joshua Slive <[EMAIL PROTECTED]> wrote:
On 10/19/05, Joe A <[EMAIL PROTECTED]> wrote:
> What would cause apache2 to occasionally become unresponsive? SAR isn't> reporting any heavy load for the 10 minute period during which it crashed
On 10/19/05, Joe A <[EMAIL PROTECTED]> wrote:
> What would cause apache2 to occasionally become unresponsive? SAR isn't
> reporting any heavy load for the 10 minute period during which it crashed...
> apparently when it was unresponsive there was "just one single apache thread
> running"
Usually a
What would cause apache2 to occasionally become unresponsive? SAR isn't
reporting any heavy load for the 10 minute period during which it
crashed... apparently when it was unresponsive there was "just one
single apache thread running"
