From 7ffe4b90220045eefdeb830213489d79c4fdc0bb Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Thu, 26 May 2011 13:40:46 +0000 Subject: Mention that the error log format is now configurable. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1127905 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/logs.xml | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) (limited to 'docs/manual/logs.xml') diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml index a762d9d2c4..6c01ae7136 100644 --- a/docs/manual/logs.xml +++ b/docs/manual/logs.xml @@ -112,7 +112,7 @@ syslog or pipe them to a program.

-

The format of the error log is relatively free-form and +

The default format of the error log is relatively free-form and descriptive. But there is certain information that is contained in most error log entries. For example, here is a typical message.

@@ -140,14 +140,12 @@ information written to stderr by a CGI script will be copied directly to the error log.

-

It is not possible to customize the error log by adding or - removing information. However, error log entries dealing with - particular requests have corresponding entries in the access log. For example, the above example - entry corresponds to an access log entry with status code 403. - Since it is possible to customize the access log, you can - obtain more information about error conditions using that log - file.

+

Using the ErrorLogFormat + directive, you can customize the format of the error log, and what + values are logged. If you have mod_unique_id, you + can put a %L token in both the error log and the access + log, producing a log entry ID with which you can correlate the entry + in the error log with the entry in the access log.

During testing, it is often useful to continuously monitor the error log for any problems. On Unix systems, you can -- cgit v1.2.3