Log file
W3Perl is running with the COMMON logfile format. It also run
with the extended common format used by NCSA 1.5
Huge log file
It would be faster if you decide to crunch your logifle each month.
Instead of scanning a huge log file, the package will only scan
about the current month log file.
How to build monthly crunched log file is explain
here
One day log
The package require that the logfile have more than one day's data.
But if your site is pretty busy and you decide to clear the log files each day,
it's still possible to use w3perl.
Follow the next instructions.
- At midnight, move your current logfile to logfile.old
- First day, run cron-pages.pl.
Next day use cron-inc.pl....
Cron-inc.pl will scan only the previous day so you need only to
keep the previous day log and then destroy it.
- Don't forget to run also cron-hour every hour, cron-jour once a day,
cron-semaines once a week.
You can't use cron-mois.pl, sorry.
Example :
Day 1
log file logdata is running from 00 h to 23 h 59
Day 2
"mv logdata logw3" at 00 h 00
log file logdata is running from 00 h to 23 h 59
run cron-pages.pl (scanning the logw3 file) and then rm logw3
Day 3
"mv logdata logw3" at 00 h 00
log file logdata is running from 00 h to 23 h 59
run cron-inc.pl (scanning the logw3 file) and then rm logw3
Day 4
same as Day 3
....
You will have incremental stats with only a one day logfile.
Perhaps you can loose some requests around minight.
