Re: [cobalt-users] Webalizer & Logrotate, lets try it again...

["Steven Werby" <steven-lists@xxxxxxxxxxxx>]

Debbie Doerrlamm <wkdwich@xxxxxxxxxxxx> wrote:
> It does not state if it will ungz the logs or not that I can find.. Does
> anyone know that??

Haven't used this feature yet (only available in most recent version), but Webalizer
is supposed to handle the logs in the compressed (gzipped) state with no intervention
on your part.  I believe it's only looking for gzipped files of the same name as an
existing regular log file, but consult the manual.  If you don't have the manual in
the package installation check webalizer.com for the online version.

> So I think I need to remove webalizer.pl from the cron.daily directory,
> place it elsewhere's.. then add a line to the cron to run it daily.. after
> the logrotate or ideally before?? Or is there another solution I'm missing
> here..

I don' think you have to move the webalizer script.

> The comment line in webalizer.pl states it depends on the conf file being
> in /etc, so that stays and no adjustments to the .pl is needed at all..
> just change the cron to use the -p switch.. can anyone help me out on that
> string please??

Is your webalizer.conf file at /etc/webalizer.conf?  It should be unless the .pl
script specifies a different webalizer.conf location.  That's useful if you want to
use different conf files for each virtual site.  I imagine the webalizer.pl file
contains a number of lines with a component similar to:

/usr/local/bin/webalizer -Q -n www.domain.com -o /home/sites/site1/stats \

The -p switch is added in this line.  "man webalizer" and webalizer --help for more
info.

> I never saw the "run-parts" in a cron before.. I assume it runs everything
> in that directory?? That's what it means?

Exactly.  It's pretty useful if you have a lot of scripts you want to run from a
crontab at the same time.

> Thanks... learning new stuff every day.. frustrating but rewarding :)

So, what did you learn at school today?  <smile>

Steven Werby {steven-lists@xxxxxxxxxxxx}