httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject cvs commit: httpd-2.0/docs/manual/mod mod_log_forensic.xml
Date Mon, 12 Apr 2004 17:23:20 GMT
nd          2004/04/12 10:23:20

  Added:       docs/manual/mod Tag: APACHE_2_0_BRANCH mod_log_forensic.xml
  Log:
  mod_log_forensic is now in 2.0
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.3.2.1   +14 -5     httpd-2.0/docs/manual/mod/mod_log_forensic.xml
  
  Index: mod_log_forensic.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_log_forensic.xml,v
  retrieving revision 1.3
  retrieving revision 1.3.2.1
  diff -u -u -r1.3 -r1.3.2.1
  --- mod_log_forensic.xml	12 Apr 2004 17:22:27 -0000	1.3
  +++ mod_log_forensic.xml	12 Apr 2004 17:23:20 -0000	1.3.2.1
  @@ -25,8 +25,7 @@
   <status>Extension</status>
   <sourcefile>mod_log_forensic.c</sourcefile>
   <identifier>log_forensic_module</identifier>
  -<compatibility><module>mod_unique_id</module> is no longer required since
  -version 2.1</compatibility>
  +<compatibility>Available in version 2.0.50 and later</compatibility>
   
   <summary>
       <p>This module provides for forensic logging of client
  @@ -46,6 +45,13 @@
       <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>
  +
  +    <note type="warning">
  +      This module was backported from version 2.1 which uses a more powerful
  +      APR version in order to generate the forensic IDs. If you want to run
  +      <module>mod_log_forensic</module> in version 2.0, you need to include
  +      <module>mod_unique_id</module> as well.
  +    </note>
   </summary>
   <seealso><a href="../logs.html">Apache Log Files</a></seealso>
   <seealso><module>mod_log_config</module></seealso>
  @@ -105,9 +111,12 @@
       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 <directive module="mod_log_config">CustomLog</directive>
  -    directive. <module>mod_log_forensic</module> 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>
  +    directive. <module>mod_log_forensic</module> takes the unique ID from
  +    <module>mod_unique_id</module>, so you need to load this module as well.
  +    (This requirement will not be necessary in version 2.1 and later, because
  +    of a more powerful APR version.) The ID token is attached to the request
  +    under the name <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
       the logs will be written, can take one of the following two
  
  
  

Mime
View raw message