httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37026] - Child process enters infinite loop
Date Wed, 12 Oct 2005 13:32:23 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37026>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37026





------- Additional Comments From rpluem@apache.org  2005-10-12 15:32 -------
Argh. Stupid error of mine. The truss output cannot tell you in general if there
is extensive CPU consumption or not. It only assures you (in this case) that the
CPU consumption you see is not burned in kernel mode, because there is only a
small number of syscalls in the 100 secs you observed the process. To find out
which lwp (a.k.a thread) of the process is actually burning CPU you can use
prstat -L -p <pid>.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message