You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2004/02/25 06:36:04 UTC
cvs commit: httpd-2.0/docs/manual/mod mod_log_forensic.html.en
nd 2004/02/24 21:36:04
Modified: docs/manual/mod mod_log_forensic.html.en
Log:
update transformation
Revision Changes Path
1.2 +14 -14 httpd-2.0/docs/manual/mod/mod_log_forensic.html.en
Index: mod_log_forensic.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_log_forensic.html.en,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -u -r1.1 -r1.2
--- mod_log_forensic.html.en 21 Feb 2004 17:44:27 -0000 1.1
+++ mod_log_forensic.html.en 25 Feb 2004 05:36:04 -0000 1.2
@@ -32,20 +32,20 @@
<p>This module provides for forensic logging of client
requests. Logging is done before and after processing a request, so the
forensic log contains two log lines for each request.
- The forensic logger works very strict, which means:</p>
+ The forensic logger is very strict, which means:</p>
<ul>
<li>The format is fixed. You cannot modify the logging format at
runtime.</li>
- <li>If it cannot write its data, the particular child process
- exits immediately and possibly dumps core (depends on your
+ <li>If it cannot write its data, the child process
+ exits immediately and may dump core (depending on your
<code class="directive"><a href="../mod/mpm_common.html#coredumpdirectory">CoreDumpDirectory</a></code>
configuration).</li>
</ul>
- <p>In order to evaluate the log output there's a script
- <code>check_forensic</code>, which can be found in the support directory
- of the distribution.</p>
+ <p>The <code>check_forensic</code> script, which can be found in the
+ distribution's support directory, may be helpful in evaluating the
+ forensic log output.</p>
</div>
<div id="quickview"><h3 class="directives">Directives</h3>
<ul id="toc">
@@ -69,9 +69,9 @@
where normal logging occurs.</p>
<p>In order to identify each request, a unique request ID is assigned.
- This forensic id can be cross logged in the normal transfer log using the
+ This forensic ID can be cross logged in the normal transfer log using the
<code>%{forensic-id}n</code> format string. If you're using
- <code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code> its generated ID will be used.</p>
+ <code class="module"><a href="../mod/mod_unique_id.html">mod_unique_id</a></code>, its generated ID will be used.</p>
<p>The first line logs the forensic ID, the request line and all received
headers, separated by pipe characters (<code>|</code>). A sample line
@@ -86,13 +86,13 @@
<p>The plus character at the beginning indicates that this is first log
line of this request. The second line just contains a minus character and
- the id again:</p>
+ the ID again:</p>
<div class="example"><p><code>
-yQtJf8CoAB4AAFNXBIEAAAAA
</code></p></div>
- <p>The <code>check_forensic</code> script gets as its argument the name
+ <p>The <code>check_forensic</code> script takes as its argument the name
of the logfile. It looks for those <code>+</code>/<code>-</code> ID pairs
and complains if a request was not completed.</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
@@ -114,11 +114,11 @@
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in version 2.1 and later</td></tr>
</table>
<p>The <code class="directive">ForensicLog</code> directive is used to
- log requests to the server for a forensic analysis. Each log entry
- gets assigned unique id which can be associated with the request
+ log requests to the server for forensic analysis. Each log entry
+ is assigned a unique ID which can be associated with the request
using the normal <code class="directive"><a href="../mod/mod_log_config.html#customlog">CustomLog</a></code>
- directive. <code class="module"><a href="../mod/mod_log_forensic.html">mod_log_forensic</a></code> leaves a note called
- <code>forensic-id</code> which can be added to the transfer log by
+ directive. <code class="module"><a href="../mod/mod_log_forensic.html">mod_log_forensic</a></code> creates a token called
+ <code>forensic-id</code>, which can be added to the transfer log
using the <code>%{forensic-id}n</code> format string.</p>
<p>The argument, which specifies the location to which