From: Jason S. Lingohr Date: Fri, 12 Oct 2007 00:13:49 +0000 (+0000) Subject: Changes as suggested by Lucien Gentis. X-Git-Tag: 2.3.0~1332 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=86c8c85302b7ad52cb06065fc7c8131f6168fdde;p=apache Changes as suggested by Lucien Gentis. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@583991 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml index 70930e6f57..3f44d2c0ca 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -72,8 +72,8 @@ what went wrong and how to fix it.

The error log is usually written to a file (typically - error_log on unix systems and - error.log on Windows and OS/2). On unix systems it + error_log on Unix systems and + error.log on Windows and OS/2). On Unix systems it is also possible to have the server send errors to syslog or pipe them to a program.

@@ -90,11 +90,11 @@

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 LogLevel 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.

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: