You need to point the conf file to the logs from your webserver. You may want to add this as a cron job for regularly updated stats. (Add other information here... work in progress)
For 4.20beta Use ipkg install webalizer Ignore the S99webalizer notice You need to create a folder example stats in your apache web folder for example /opt/share/www/stats edit the webalizer.conf file in /opt/etc
-directory of the access log /opt/var/apache2/log/access_log -directory of the output folder /opt/share/www/stats -Most likely the Hostname to example.com
Create a symbolic link of the webalizer.conf in the /opt/bin folder (this is where the webalizer command is) Create a crontab to issue a webalizer command whatever your interval is.
Issue the webalizer command - "/opt/etc/webalizer /opt/var/apache2/log/access_log" Check the output and the folder/file commands to be viewable.
Added by Dutch, on 13-Jun-2005:
Here's what I did for 3.18beta, which strongly resembles the above instructions:
Ignore the notice about S99webalizer, as the install does not create this file, and it is not needed anyway.
Create a folder under your web root to contain the webalizer output. This is important, as it creates an index.html and several other files, which will overwrite like-named files that exist its output folder. I'll give you three guesses as to how I found that out.... :^)
Edit the webalizer.conf file to tell it where your apache log file is stored, per the instructions at the end of the webalizer install. Also make sure to tell it where to put the webalizer output.
Create a script in the /etc directory, and call update-webalizer-stats (or whatever you think you should call it--you could call it "Fred" if you really want to), using this code:
This script will automate the process of running the webalizer with your webalizer.conf file (assuming it's in /share/hdd/conf/opt/etc, which is the default location--change path as necessary if you moved it, of course....)
You can then just type the command
Edit your crontab, adding a line like this one, which runs the script you created on the 13th minute of every hour:
...or like this, to run at 11:59 PM every day
...or like this, to run at 12:01 AM on the first of every month
Of course, if you named your script "Fred", you'll want to change the filename in the crontab line to match that.... :^)
Chmod your webalizer output directory to 755.
>> mySlug 07/2006: anybody tried the revese DNS lookup option yet? With me it only produces the messages
Looks like the bin/webalizer generated program is not linked to ant libdb file (http://mail-index.netbsd.org/pkgsrc-bugs/2004/11/16/0018.html(approve sites))...anybody tried to fix this already?
die_Amme: For OpenSlug 3.10:
ipkg install db-dev
build webalizer with
./configure --with-db=/usr/include --with-dblib=/usr/lib --enable-dns
But there are nevertheless still errors, unable to open dns_cache.db ...
>> JacobRale? November 6, 2008 I had a little bit of trouble with this. I think you might need to change !/bin/bash to !/bin/sh if you don't have bash installed. Alternatively install bash including creating a /etc/shells file. (See http://www.nslu2-linux.org/wiki/HowTo/InstallingBash). After that it went pretty smoothly, though I did have to install a few packages. (You might want to try ipkg-web; sometimes the mouse is easily or at least requires less thinking.)