You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by js...@apache.org on 2007/10/12 03:10:53 UTC
svn commit: r584015 - in /httpd/httpd/branches/2.2.x/docs/manual:
logs.html.en logs.xml
Author: jsl
Date: Thu Oct 11 18:10:53 2007
New Revision: 584015
URL: http://svn.apache.org/viewvc?rev=584015&view=rev
Log:
Backport of r583991.
Modified:
httpd/httpd/branches/2.2.x/docs/manual/logs.html.en
httpd/httpd/branches/2.2.x/docs/manual/logs.xml
Modified: httpd/httpd/branches/2.2.x/docs/manual/logs.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/logs.html.en?rev=584015&r1=584014&r2=584015&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/logs.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/logs.html.en Thu Oct 11 18:10:53 2007
@@ -74,8 +74,8 @@
what went wrong and how to fix it.</p>
<p>The error log is usually written to a file (typically
- <code>error_log</code> on unix systems and
- <code>error.log</code> on Windows and OS/2). On unix systems it
+ <code>error_log</code> on Unix systems and
+ <code>error.log</code> on Windows and OS/2). On Unix systems it
is also possible to have the server send errors to
<code>syslog</code> or <a href="#piped">pipe them to a
program</a>.</p>
@@ -92,11 +92,11 @@
</code></p></div>
<p>The first item in the log entry is the date and time of the
- message. The second entry lists the severity of the error being
+ message. The second item lists the severity of the error being
reported. The <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code>
directive is used to control the types of errors that are sent
to the error log by restricting the severity level. The third
- entry gives the IP address of the client that generated the
+ item gives the IP address of the client that generated the
error. Beyond that is the message itself, which in this case
indicates that the server has been configured to deny the
client access. The server reports the file-system path (as
@@ -117,7 +117,7 @@
file.</p>
<p>During testing, it is often useful to continuously monitor
- the error log for any problems. On unix systems, you can
+ the error log for any problems. On Unix systems, you can
accomplish this using:</p>
<div class="example"><p><code>
Modified: httpd/httpd/branches/2.2.x/docs/manual/logs.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/logs.xml?rev=584015&r1=584014&r2=584015&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/logs.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/logs.xml Thu Oct 11 18:10:53 2007
@@ -72,8 +72,8 @@
what went wrong and how to fix it.</p>
<p>The error log is usually written to a file (typically
- <code>error_log</code> on unix systems and
- <code>error.log</code> on Windows and OS/2). On unix systems it
+ <code>error_log</code> on Unix systems and
+ <code>error.log</code> on Windows and OS/2). On Unix systems it
is also possible to have the server send errors to
<code>syslog</code> or <a href="#piped">pipe them to a
program</a>.</p>
@@ -90,11 +90,11 @@
</example>
<p>The first item in the log entry is the date and time of the
- message. The second entry lists the severity of the error being
+ message. The second item lists the severity of the error being
reported. The <directive module="core">LogLevel</directive>
directive is used to control the types of errors that are sent
to the error log by restricting the severity level. The third
- entry gives the IP address of the client that generated the
+ item gives the IP address of the client that generated the
error. Beyond that is the message itself, which in this case
indicates that the server has been configured to deny the
client access. The server reports the file-system path (as
@@ -116,7 +116,7 @@
file.</p>
<p>During testing, it is often useful to continuously monitor
- the error log for any problems. On unix systems, you can
+ the error log for any problems. On Unix systems, you can
accomplish this using:</p>
<example>