Apache-Logmonster
view release on metacpan or search on metacpan
logmonster.conf view on Meta::CPAN
# Logmonster configuration file
##
# Logbase - path to web logs. Logmonster will determine where
# logs are based upon $logbase and the date being processed.
#
# Use cronolog or something like it. Apache recommends it:
#
# http://httpd.apache.org/docs/misc/FAQ-I.html#rotate
#
# Apache 2.0 expands cronolog support by allowing ErrorLogs to be
# piped to cronolog as well.
##
logbase = /var/log/http
##
# log file owner - the user and group that owns the Apache log files
##
log_user = www
log_group = www
##
# tmpdir - the place where logmonster can create temp files. Make sure this
# directory exists.
##
tmpdir = /var/log/http/tmp
##
# etc_dir - directory where awstats config files are stored.
##
confdir = /etc/awstats
##
# statsdir - directory where awstats DB files are stored.
##
statsdir = /var/db/awstats
##
# userlogs - some users want access to their raw HTTP logs. If you host
# their site on multiple servers and log directly to their home
# directory (from each server), they end up with several log
# files, not in sequential order, and log processors can't deal
# with that. Instead, send the logs off to /var/log/apache and
# at the end of each period, Logmonster will collect the logs
# from each server, merge them, feed them through the processor
# of your choice, and then drop the logs into the userlogs dir
# within DocumentRoot.
#
# I would recommend putting the userlogs outside the DocumentRoot
# eg ../logs (Yes it works) so the logs are inaccessible via http.
# --Gernot Hueber
##
userlogs = logs
##
# access - What your http access logs are named. This needs to match the
# filename given in the CustomLog directive of httpd.conf
##
access = access.log
##
# error - What your http error logs are named. This needs to match the
# filename given in the ErrorLog directive of httpd.conf
##
( run in 0.561 second using v1.01-cache-2.11-cpan-97f6503c9c8 )