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.
What can I do to force that the logs will be generated ?
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 _________________________________________________________________Join the world?s largest e-mail service with MSN Hotmail. http://www.hotmail.com