AW: [cobalt-users] web.log zero size and webalizer

["Loneboy" <loneboy@xxxxxxxxxxx>]

Well, thanks WS
i just did it your way, but I thought there must be some
elegant way to handle this behaviour. That's not computerlike
to check the log manually :-) There are 1000s of RaQ/webalizer
combos in the world and they all have the same problem,
anybody who has the working script or so ?

PS

----------------------------------------------------------------------------
>Your information is correct and there is likely more than one way to handle
>it. Setting your logs to rotate less often is one way. I use a dumb trick
on
>sites that I care about knowing. You can rename the web.log to
web.log.save,
>then rename web.log.1.gz to web.log.gz gunzip it, run webalizer manually,
>then reverse the process. As long as you do this on the day that the logs
>rotated, before the next webalizer cycle, it seems to work. You could, if
>you were smarter than me, write a script to do the above and run it as a
>cron job...

>I think you could also set the logs to rotate on a specific time schedule
>and work around it that way.. but it is normal to have it doing what it is
>doing.

>WS

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Pierre Stoll wrote:
I have a RaQ3 with webalizer 2.01-06 and now on the bigger sites
there's this little problem, that the web.log has 0 byte size
and therefore the webalizer stats for that specific day show
nothing.

I searched the archive and found that a web.log.1.gz (which
is really there) will be created when the logfile would be
too large and then over site quota. I've also read that the
log may be max. 10% of the site quota.

I just want to know - is my information right ?

What can I do to force that the logs will be generated ?

What about the log size entry in /etc/logrotate.d ? Important ?

What about the "zapache" trick in /etc/logrotate.d ?


Thanks for any help,
Pierre Stoll