Automatic/manual use
Manual
Execute the program at the commands line. Use '-h' to see options available.
After having configured the config.pl script, you can run cron-pages.pl.
Wait for the process to finish and check the result.
Never use again cron-pages now, use instead cron-inc.pl, it will compute
incremental stats by scanning only the previous day.
Cron-inc is able to scan the 7 last previous day, so you don't have to run it daily
if you want. If you forget to run it for a week or more, run cron-pages or use the
-s option in cron-inc (but it will be faster to use cron-pages if you are very late).
So run :
- cron-pages for the first time or if you forget to run cron-inc for a while.
- cron-inc for a daily incremental stats
Then run :
- cron-hour to have hourly stats (each hour)
- cron-jour to have daily stats (once a day)
- cron-semaines to have weekly stats (once a week)
- cron-mois to have monthly stats (once a month)
Except for hourly stats, the results will be updated from the last time you ran
the scripts...you won't loose any data if you don't run the scripts every day.
If you don't see a link for the monthly or weekly stats, the reason is your logfile
doesn't contains enough data to compute them at the moment.
To have more informations, you can run optionnal scripts :
- cron-agent to have agent stats
- cron-refer to have referer stats
- cron-url to have stats about your web pages (a map between url and name of the HTML document is also done)
- cron-session to have session stats
- cron-error to have error stats
You can run them when you want ; once a week is enough for me.
You will need to wait a day for having a link from the homepage as the update is made by cron-inc.
Automatic
You should have permission to execute cron commands (ask your administration
system if you can't). You need to write the full pathname for the files to run.
In your crontab file, you could write :
| Core scripts |
| 10 00 * * * |
/norfolk/www/w3perl/cron-inc.pl > /dev/null 2>&1 |
| 01 * * * * |
/norfolk/www/w3perl/cron-hour.pl > /dev/null 2>&1 |
| 00 01 * * * |
/norfolk/www/w3perl/cron-jour.pl > /dev/null 2>&1 |
| 30 01 * * 1 |
/norfolk/www/w3perl/cron-semaines.pl > /dev/null 2>&1 |
| 00 02 1 * * |
/norfolk/www/w3perl/cron-mois.pl > /dev/null 2>&1 |
- Cron-inc will be run each night at 00:10, it should be the first
to run as it produces results files for the other programs except cron-hour.pl
You should have run cron-pages.pl once before after installing the package !
- Cron-hour.pl is running every hour.
- Others programs should be run later when cron-inc has finished its works.
| Optionnal scripts |
| 03 00 * * 1 |
/norfolk/www/w3perl/cron-url.pl > /dev/null 2>&1 |
| 30 02 * * 1 |
/norfolk/www/w3perl/cron-session.pl > /dev/null 2>&1 |
| 35 03 * * 1 |
/norfolk/www/w3perl/cron-agent.pl > /dev/null 2>&1 |
| 40 03 * * 1 |
/norfolk/www/w3perl/cron-refer.pl > /dev/null 2>&1 |
| 45 03 * * 1 |
/norfolk/www/w3perl/cron-error.pl > /dev/null 2>&1 |
- Cron-url.pl will output a file for URL to document's title conversion.
You could run it every day just before cron-inc.pl. I've choose to run it
only once a week as I don't have a lots of new html pages every day !
- cron-refer, cron-agent don't have to be run if you don't use a httpd which
log the referer and agent informations.
- Cron-session can take a while if you have very large log file.
If your results files have problems, delete the redirection output ('> /dev/null 2 > &1').
You will receive an email on the morning telling you what's wrong.
