NSLU2-Linux
view · edit · print · history

Optware.Webalizer History

Hide minor edits - Show changes to markup

November 09, 2008, at 02:15 AM by Jacobrale --
Changed line 87 from:

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 pacages. (You might want to try ipkg-web; sometimes the mouse is easily or requires less thinking.)

to:

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.)

November 09, 2008, at 02:12 AM by Jacobrale --
Changed line 87 from:

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). Even then, I got complaints about a missing libdb-4.2.so. Which as noted above, weren't solved easily. (I could not install db-dev either, so...)

to:

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 pacages. (You might want to try ipkg-web; sometimes the mouse is easily or requires less thinking.)

November 08, 2008, at 01:37 AM by Jacobrale --
Added lines 85-87:

>> 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). Even then, I got complaints about a missing libdb-4.2.so. Which as noted above, weren't solved easily. (I could not install db-dev either, so...)

July 23, 2006, at 08:11 PM by die amme --
Changed lines 77-84 from:

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)...anybody tried to fix this already?

to:

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)...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 ...

July 10, 2006, at 05:31 AM by mySlug -- Reverse DNS lookup doesn\'t work
Changed lines 72-77 from:

to:

>> mySlug 07/2006: anybody tried the revese DNS lookup option yet? With me it only produces the messages

@@Warning: Invalid keyword 'DNSCache?' (webalizer.conf)
@@Warning: Invalid keyword 'DNSChildren?' (webalizer.conf)

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)...anybody tried to fix this already?

June 15, 2005, at 06:14 PM by Dutch --
Changed lines 70-71 from:

Chmod all the files in your webalizer output directory to 644, and make sure the directory itself is chmodded to 755.

to:

Chmod your webalizer output directory to 755.

June 15, 2005, at 06:13 PM by Dutch --
Changed line 35 from:
to:
#
Changed lines 37-38 from:
cd /share/hdd/conf/opt/etc
webalizer
to:
cd /share/hdd/conf/opt/etc # change this to the location your webalizer.conf
webalizer -q
#
cd /share/hdd/data/html/stat # change this to the location of your webalizer output files
chmod 644 *.html
chmod 644 *.png
#
Changed lines 45-46 from:
to:
Changed lines 56-57 from:

...or like this, to run at 11:59 AM every day

to:

...or like this, to run at 11:59 PM every day

Changed line 59 from:
59 11 * * * root /etc/update-webalizer-stats &>/dev/null
to:
59 23 * * * root /etc/update-webalizer-stats &>/dev/null
Added lines 62-67:

...or like this, to run at 12:01 AM on the first of every month

1 0 1 * * root /etc/update-webalizer-stats &>/dev/null
Changed lines 72-73 from:

PS: Any tips anyone has on automating the chmodding of the files in the output directory in a script (or on forcing webalizer to create them chmodded to 644 by default) are welcome at this point, as I don't know how to do either trick yet.... :^)

to:

June 14, 2005, at 11:07 PM by Dutch --
Changed lines 30-31 from:

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.

to:

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.

Changed lines 52-53 from:

...or like this, to run at 11:59 PM every day

to:

...or like this, to run at 11:59 AM every day

June 14, 2005, at 05:18 PM by Dutch --
Changed lines 62-63 from:

PS: Any tips anyone has on automating the chmodding of the files in the output directory in a script (or on forcing webalizer to create them chmodded to 644 by default) are welcome at this point, as I don't know how to do eitehr trick yet.... :^)

to:

PS: Any tips anyone has on automating the chmodding of the files in the output directory in a script (or on forcing webalizer to create them chmodded to 644 by default) are welcome at this point, as I don't know how to do either trick yet.... :^)

June 14, 2005, at 12:21 AM by Dutch --
Changed lines 44-45 from:

You can then just type the command /etc/update-webalizer-stats and it will redraw the webalizer pages and graphics with the current stats.

to:

You can then just type the command /etc/update-webalizer-stats and it will redraw the webalizer pages and graphics with the current stats.

June 14, 2005, at 12:16 AM by Dutch --
Added lines 44-45:

You can then just type the command /etc/update-webalizer-stats and it will redraw the webalizer pages and graphics with the current stats.

June 14, 2005, at 12:12 AM by Dutch --
Added lines 16-61:

Added by Dutch, on 13-Jun-2005:

Here's what I did for 3.18beta, which strongly resembles the above instructions:

ipkg install webalizer

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.

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:

#!/bin/bash
currentLoc=$PWD
cd /share/hdd/conf/opt/etc
webalizer
cd $currentLoc

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....)

Edit your crontab, adding a line like this one, which runs the script you created on the 13th minute of every hour:

13 * * * * root /etc/update-webalizer-stats &>/dev/null

...or like this, to run at 11:59 PM every day

59 11 * * * root /etc/update-webalizer-stats &>/dev/null

Of course, if you named your script "Fred", you'll want to change the filename in the crontab line to match that.... :^)

Chmod all the files in your webalizer output directory to 644, and make sure the directory itself is chmodded to 755.

PS: Any tips anyone has on automating the chmodding of the files in the output directory in a script (or on forcing webalizer to create them chmodded to 644 by default) are welcome at this point, as I don't know how to do eitehr trick yet.... :^)

May 27, 2005, at 10:05 PM by J -- 4.20b commands
Changed lines 1-15 from:

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)

to:

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.

April 27, 2005, at 09:00 PM by ChrisE --
Added line 1:

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)

view · edit · print · history · Last edited by Jacobrale.
Based on work by Jacobrale, die amme, mySlug, Dutch, and J.
Originally by ChrisE.
Page last modified on November 09, 2008, at 02:15 AM