From 13a83c6f84fc071eb4ec7e75a85d3f74e1cbd3a9 Mon Sep 17 00:00:00 2001
From: "Jason S. Lingohr"
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.
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
@@ -117,7 +117,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:
diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de
index 747f686e84..b8f463cc40 100644
--- a/docs/manual/mod/core.xml.de
+++ b/docs/manual/mod/core.xml.de
@@ -1,7 +1,7 @@
-
+
+
+
+
+