On Fri, Oct 26, 2007 at 01:28:31PM -0500, Steve Yates wrote:
Ron Richey wrote on 10/26/2007 12:44:52 PM:
So, each entry now looks something like this:
@daily root savelogs --apacheconf=/www/conf/httpd.conf
--apachehost=subhosteddomain.com --
postmovehook="/www/bin/apachectl restart"
--period=7 --chown=accountname:
If I'm not mistaken having "apacheconf" will process all logs,
so if that is on each cron entry it will try to process all logs for
each job?
"If you specify this option, giving it a valid httpd.conf file, savelogs
will parse your Apache configuration file looking for standard log file
directives. Any files found will be processed."
The ApacheHost option will exclude everything found in ApacheConf
except for the specified logs:
ApacheHost
This option tells savelogs which logs to select out of
the Apache configuration file (as specified by the
ApacheConf directive) based on the Apache ServerName
directive in the VirtualHost block. If this option is
set, only logs for matching hosts will be rotated
(this applies only to logs found in the Apache config-
uration file; other logs specified in other ways
(e.g., on the command-line or via the Log directive)
will be processed as usual).
Example:
savelogs --apacheconf=/www/conf/httpd.conf --apachehost=foo.com
or in your configuration file:
ApacheConf /www/conf/httpd.conf
ApacheHost foo.com
The ApacheHost directive may be specified multiple
times to process logs for multiple virtual hosts. If
no logs are found in the Apache VirtualHost block, no
logs will be rotated for that virtual host.
We normally disable log rotation in CPX and just use one cron job to
process them all.
That's probably the best option, imo. Otherwise (the way CPX currently
sets it up) you're restarting Apache once for each virtualhost entry,
which for some of you who host hundreds of sites can be a little hard
on a server.
Scott