From 3ac83804bc25d7e53b4afb4693c42b99a7210257 Mon Sep 17 00:00:00 2001
From: Rich Bowen <rbowen@apache.org>
Date: Sun, 2 Aug 2015 20:52:55 +0000
Subject: [PATCH] Example of how to invoke the forensic log

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1693826 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/mod_log_forensic.xml | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/docs/manual/mod/mod_log_forensic.xml b/docs/manual/mod/mod_log_forensic.xml
index 6398e22ab4..c661490105 100644
--- a/docs/manual/mod/mod_log_forensic.xml
+++ b/docs/manual/mod/mod_log_forensic.xml
@@ -29,8 +29,16 @@
 <identifier>log_forensic_module</identifier>
 
 <summary>
-    <p>This module provides for forensic logging of client
-    requests. Logging is done before and after processing a request, so the
+    <p>This module provides for forensic logging of client requests.</p>
+
+    <p>Create the log file using the <directive>ForensicLog</directive>
+    directive:</p>
+
+    <highlight language="config">
+    ForensicLog logs/forensic_log
+    </highlight>
+    
+    <p>Logging is done before and after processing a request, so the
     forensic log contains two log lines for each request.
     The forensic logger is very strict, which means:</p>
 
@@ -44,8 +52,8 @@
     </ul>
 
     <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>
+    distribution's support directory, processes the resulting log file
+    to identify the requests that didn't complete.</p>
 </summary>
 <seealso><a href="../logs.html">Apache Log Files</a></seealso>
 <seealso><module>mod_log_config</module></seealso>
-- 
2.50.1