Limitations
|
Some come from the OS, others are due to W3Perl itself.
- On system with restricted length filename (MacOS 9, Win3.11 or RiscOS), you
can't use the highest level of precision which is 4.
- Your logfile should have at least one request by week. If not, date may shift.
- You need at least Perl 5 in order to parse logfile
larger than 2 Gb (or you need to split your logfile). If you need ipv6
parsing, use Perl 5.14 or you will need to install the Socket6 perl module.
- URL mapping may fail with some awful HTML files (Bill, buy
a HTML book please !). This cron-url.pl script is not required to
compute stats.
- You need to get logfile at least two days long to compute
something (due to incremental work). If you have just started your
webserver, wait tomorrow !
- W3Perl will exit if date format is not the english one (answer : export LANG="eng" or setenv LANG eng)
- W3Perl find
unknown countries
code. With generic tld, it will be worse ! :(
- W3Perl can't cope with more than 120 crunched logfiles or 10 years of logfiles. If
you plan to get stats over the last 10 years, tell me !
|