Javier Gostling wrote:
yup... thought about that as well.. (by the way..i use sarg for the squid processing).. but since i'am going to do daily, weekly and monthly reports...including squidguard... i would have to do more scripting than for the lock file solution :)Not that tough. I have my squid log files rotate on a weekly basis with compression enabled. For my monthly reports, I just create a big log file by zcatting the old logfiles and catting the current logfile into a temporary logfile to be processed.
I also use sarg. I found the daily, weekly and monthly scripts that came with it quite defficient, so I wrote my own scripts to do the same job. None of the scripts are over 1Kb. in size. If there is interest, I can post them to the list.
yeah.. i'am definitly interested !!
Yep... but thats not the case in my situation.. i just want daily weekly and monthly reports (including the squidGuard logs) without conflicting the logfile rotation process... but with still remaining the date integrity of the generated reports (don't miss some says due to a logrotation which took place just at a bad time :) )!i already do that actualy :) i do daily reports, separate weekly and separate monthly reports :)is there no better solution?Can you do partial data collection on a more frequent basis? Perhaps weekly? That way your processing time should be drastically reduced.
Ok. Another solution we use for our bigger servers is to have the log files shipped off server periodicaly. then all processing happens in this offline location, where logfile rotation is not an issue. This has the added benefit of lightening the load on the servers.
Cheers Marcel
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
