From: Rainer Jung As with conditional logging, piped logs are a very powerful
tool, but they should not be used where a simpler solution like
off-line post-processing is available. By default the piped log process is spawned using a shell.
+ (usually with Use " If the file-path
- begins with a pipe (|) then it is assumed to be a command to spawn
- to handle the error log./bin/sh -c
).
+ Depending on the shell specifics invocation via shell might
+ lead to an additional shell process for the lifetime of the
+ logging pipe program and signal handling problems during
+ restart.||
" instead of "|
"
+ to spawn without invoking a shell:
+ CustomLog "||/usr/local/apache/bin/rotatelogs
+ /var/log/access_log 86400" common
+ |
" then it is assumed to be a
+ command to spawn to handle the error log.
See the notes on piped logs for + more information.
+Using syslog
instead of a filename enables logging
via syslogd(8) if the system supports it. The default is to use
syslog facility local7
, but you can override this by
diff --git a/docs/manual/mod/mod_log_config.xml b/docs/manual/mod/mod_log_config.xml
index 69ce28e28fd..e1802617bcc 100644
--- a/docs/manual/mod/mod_log_config.xml
+++ b/docs/manual/mod/mod_log_config.xml
@@ -377,7 +377,8 @@
|
", followed by the path
to a program to receive the log information on its standard
- input.
+ input. See the notes on piped logs
+ for more information.
If a program is used, then it will be run as the user who