You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2010/09/25 17:57:42 UTC
svn commit: r1001245 - in /httpd/httpd/trunk/docs/manual: logs.html.en
logs.xml
Author: rbowen
Date: Sat Sep 25 15:57:41 2010
New Revision: 1001245
URL: http://svn.apache.org/viewvc?rev=1001245&view=rev
Log:
A note about per-module logging.
Modified:
httpd/httpd/trunk/docs/manual/logs.html.en
httpd/httpd/trunk/docs/manual/logs.xml
Modified: httpd/httpd/trunk/docs/manual/logs.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/logs.html.en?rev=1001245&r1=1001244&r2=1001245&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/logs.html.en (original)
+++ httpd/httpd/trunk/docs/manual/logs.html.en Sat Sep 25 15:57:41 2010
@@ -36,6 +36,7 @@
<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#overview">Overview</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#security">Security Warning</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#errorlog">Error Log</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#permodule">Per-module logging</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#accesslog">Access Log</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#rotation">Log Rotation</a></li>
<li><img alt="" src="./images/down.gif" /> <a href="#piped">Piped Logs</a></li>
@@ -151,6 +152,34 @@
</code></p></div>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<div class="section">
+<h2><a name="permodule" id="permodule">Per-module logging</a></h2>
+
+
+ <p>The <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code> directive
+ allows you to specify a log severity level on a per-module basis. In
+ this way, if you are troubleshooting a problem with just one
+ particular module, you can turn up its logging volume without also
+ getting the details of other modules that you're not interested in.
+ This is particularly useful for modules such as
+ <code class="module"><a href="./mod/mod_proxy.html">mod_proxy</a></code> or <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code> where you
+ want to know details about what it's trying to do.</p>
+
+ <p>Do this by specifying the name of the module in your
+ <code class="directive">LogLevel</code> directive:</p>
+
+ <div class="example"><p><code>
+ LogLevel info rewrite:trace5
+ </code></p></div>
+
+ <p>This sets the main <code class="directive">LogLevel</code> to info, but
+ turns it up to <code>trace5</code> for
+ <code class="module"><a href="./mod/mod_rewrite.html">mod_rewrite</a></code>.</p>
+
+ <div class="note">This replaces the per-module logging directives, such as
+ <code>RewriteLog</code>, that were present in earlier versions of
+ the server.</div>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
<h2><a name="accesslog" id="accesslog">Access Log</a></h2>
Modified: httpd/httpd/trunk/docs/manual/logs.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/logs.xml?rev=1001245&r1=1001244&r2=1001245&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/logs.xml (original)
+++ httpd/httpd/trunk/docs/manual/logs.xml Sat Sep 25 15:57:41 2010
@@ -158,6 +158,34 @@
</example>
</section>
+ <section id="permodule">
+ <title>Per-module logging</title>
+
+ <p>The <directive module="core">LogLevel</directive> directive
+ allows you to specify a log severity level on a per-module basis. In
+ this way, if you are troubleshooting a problem with just one
+ particular module, you can turn up its logging volume without also
+ getting the details of other modules that you're not interested in.
+ This is particularly useful for modules such as
+ <module>mod_proxy</module> or <module>mod_rewrite</module> where you
+ want to know details about what it's trying to do.</p>
+
+ <p>Do this by specifying the name of the module in your
+ <directive>LogLevel</directive> directive:</p>
+
+ <example>
+ LogLevel info rewrite:trace5
+ </example>
+
+ <p>This sets the main <directive>LogLevel</directive> to info, but
+ turns it up to <code>trace5</code> for
+ <module>mod_rewrite</module>.</p>
+
+ <note>This replaces the per-module logging directives, such as
+ <code>RewriteLog</code>, that were present in earlier versions of
+ the server.</note>
+ </section>
+
<section id="accesslog">
<title>Access Log</title>