Hi,

I sort of have Webalizer working, but not exactly the way that was intended...

I copied the executable into /usr/local/bin and set the chmod to executable. At least it runs. If I go to the directory containing the log files, I can run Webalizer and it'll generate the stats (png and html files) just fine. My problem is that to view them, I have to download to my PC via ftp. As I said, not exactly the way that was intended.

1) I'll have to figure out how to set up a cron job to run Webalizer at reasonable intervals. What does everyone recommend? hourly? daily?

2) How do I set it up so that each user can view his/her stats? The way I have it now it goes bombing through one log file. What do I need to define to have each virtual server generate its own stats? (I'm using webmin)

3) What do I need to do so that each user can access their stats this way: http://www.userdomain.com/~stats (or something like this at least)?

4) Any other suggestions would be also be appreciated. How about security issues?

Thanks in advance for the help.

Originally posted by Abu Mami
1) I'll have to figure out how to set up a cron job to run Webalizer at reasonable intervals. What does everyone recommend? hourly? daily?

2) How do I set it up so that each user can view his/her stats? The way I have it now it goes bombing through one log file. What do I need to define to have each virtual server generate its own stats? (I'm using webmin)

3) What do I need to do so that each user can access their stats this way: http://www.userdomain.com/~stats (or something like this at least)?

4) Any other suggestions would be also be appreciated. How about security issues?

Thanks in advance for the help.

1) We run Webalizer (along with AWStats and MGStat) daily at 4:00am EST (the time of lowest server activity). However, Webalizer is well-written and fast, so you could run it more frequently if you desired. I wouldn't run it more than once an hour.

2) You'll have to set up a seperate crontab for each virtual server. Make it run the webalizer binary with the access_log path and output path in the command line. (We use a shell script with all of our entries in it and crontab the shell script.)

3) We just actually created a directory called 'stats' in every user's public_html directory and set up webalizer to write the stats there.

4) There aren't really any security issues with Webalizer. Just make sure your file permissions aren't too leanient. Oh and by the way, everything I've said above reflects our old server configuration - We now use a custom control panel that I wrote for users to view stats from. However this is not necessary for Webalizer to work.