/etc/sarg/sarg.conf
/etc/sarg/sarg.cron
I explained how I got sarg to work with my system. I did this by trial and errror. I experiment on a non production server. I can not say the changes I made will be trouble free.
I use mc command at root to start Midnight Commander to navigate the file system. MC makes things very easy to search, copy, edit files, etc.
Getting sarg to work requires editing several files.
First, I copied the cron job lines from sarg.cron to my crontab file and the crontab template file. I put the lines above the lines that already exist in crontab. (You can also create a copy of the template into the custom template directory which will protect the changes you make from any upgrades. Read
www.e-smith.org/custom to learn about custom templates.)
Second, if you don't reconfigure the squid logrotation script, squid will wipe the script every week which will prevent sarg from creating the monthly log. I edited the logrotate.d squid file to rotate monthly instead of weekly and changed the rotation from 5 to 2. This is working OK for me, but I am a rookie, so you might print the original settings of all files you edit, so you can restore them if necessary.
Along with this change, I edited the sarg.montly script in \usr\sbin and put a # infront of the line to rotate the squid log since this is already set up by squid.
Third, I don't understand linux file system permissions enough to mess with them, so I created an information bay called sarg. Then I edited the following files in /usr/sbin: sarg.daily, sarg.weekly, sarg.monthly. I added lines to copy the entire contents of the directory sarg stores it's reports to the info bay sarg/html directory. Note that before the line to copy the data, I have a line to first erase all files in the ibay sarg\html so my ibay sarg\html folder is always an exact copy of the default /var/www/html/squid/folders. I then put a "internet password" on the sarg ibay and can check sarg reports from anywhere.
Good luck,
2 Replies
2145 Views