Hi folks,
due to the everlasting confusion on #httpd as to what this ominous "CPU Usage"
means
in /server-status, I took a look at the source and documented it.
I unified the looks of split-logfile and log_server_status, by introducing
<code> elements around the <a>s.
And finally I documented the fact that log_server_status is a very simple
program,
which might fail in a complex setup.
This is a diff against trunk.
So long,
--
Igor Galić
Tel: +43 (0) 699 122 96 338
Fax: +43(0) 1 91 333 41
Mail: [email protected]
URL: http://brainsware.org/
Index: ../mod/mod_status.xml
===================================================================
--- ../mod/mod_status.xml (revision 910016)
+++ ../mod/mod_status.xml (working copy)
@@ -59,7 +59,7 @@
bytes per request (*)</li>
<li>The current percentage CPU used by each worker and in
- total by Apache (*)</li>
+ total by Apache as per <code>times(2)</code> (*)</li>
<li>The current hosts and requests being processed (*)</li>
</ul>
@@ -123,5 +123,21 @@
</section>
+<section id="interpretingcpu">
+
+ <title>Interpreting CPU Usage</title>
+ <p>A typical CPU Usage line looks like this:</p>
+<example>
+ CPU Usage: u5.64 s37.33 cu0 cs0 - 1.11% CPU load
+</example>
+ <p>For different MPMs this can mean different things: In a
+ <module>prefork</module>ing MPM these the are times spent in user space and
+ system space (<code>u</code> and <code>s</code>) by all the processes, as well
+ all their children (<code>cu</code> and <code>cs</code>). In a threaded
+ MPM such as <module>event</module> or <module>worker</module> the times
+ are accumulated from all involved threads.</p>
+
+</section>
+
</modulesynopsis>
Index: ../programs/index.xml
===================================================================
--- ../programs/index.xml (revision 910016)
+++ ../programs/index.xml (working copy)
@@ -89,8 +89,8 @@
<dd>Resolve hostnames for IP-addresses in Apache
logfiles</dd>
- <dt><a
- href="other.html#log_server_status">log_server_status</a></dt>
+ <dt><code><a
+ href="other.html#log_server_status">log_server_status</a></code></dt>
<dd>Periodically log the server's status</dd>
@@ -98,7 +98,7 @@
<dd>Rotate Apache logs without having to kill the server</dd>
- <dt><a href="other.html#split-logfile">split-logfile</a></dt>
+ <dt><code><a href="other.html#split-logfile">split-logfile</a></code></dt>
<dd>Split a multi-vhost logfile into per-host logfiles</dd>
Index: ../programs/other.xml
===================================================================
--- ../programs/other.xml (revision 910016)
+++ ../programs/other.xml (working copy)
@@ -37,7 +37,8 @@
something like cron. It connects to the server and downloads the status
information. It reformats the information to a single line and logs it to
a file. Adjust the variables at the top of the script to specify the
- location of the resulting logfile.</p>
+ location of the resulting logfile. This program is kept very simple and
+ will fail in a configuration where mod_security is used for instance.</p>
</section>
<section id="split-logfile"><title>split-logfile</title>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
