Ah, I see now - slightly different from what I had thought.
> My /etc/cron.daily/logrotate file looks like this:
>
> #!/bin/sh
>
> /usr/bin/analog
> /usr/bin/logrotate /etc/logrotate.conf
>
> The log rotation is being handled by the logrotate utility, using the
> params given in /etc/logrotate.conf, and I'm running analog right ahead of
> that so logs aren't "in transit" when I'm trying to parse data.
This makes sense.
Yes, I will be dealing with vhosts. So by your method I would have:
#!/bin/sh
/usr/bin/analog -G +g/path_to_cfg_file/vhost1
/usr/bin/analog -G +g/path_to_cfg_file/vhost2 # etc.
/usr/bin/logrotate /etc/logrotate.conf
and in logrotate.conf I would rollover both the analog combined_log.html
files and the combined_log files?
If the above syntax is in: /etc/cron.daily/logrotate, does that mean your
analog is running every day? Therefore placing in
/etc/cron.weekly/logrotate, makes it weekly??
One further question, does -HUP actually disable httpd? I am just
thinking that if I had say 100 sites hosted, doing 100 x -HUP signals
could be a significant downtime?
Thanks for your help.
Best regards, Brian
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
