|
Able and George,
If you have perl on your system I have a VERY easy solution for the "Giant" log file issue. I can post a script I run from the Windows Scheduler to "cut" the logs up on the fly. If you are running something other than Windows, you will have to modify the script (you will have to change the path in any event) and run it as a Cron job. It works under Windows because the log isn't "locked" but I don't know about Linux or BSD. What it does is rename the active log file to what ever convention you wat to use, how ever often you schedule it and the next SMTP transaction starts a new log. I do this for my Sendmail server also but the Sendmail & POP3 service must be stopped because they DO lock the file. I only do the Sendmail logs once a day at midnight. At this point, my SpamFilter logs are only about 40MB a day so I just let them roll over at midnight but I did try a 12 hour "cut" to make sure it would work for when the get too big.
I also schedule the to get zipped and archived once a week. As an ISP, we need to keep all logs for as long as is reasonable. We have all our mail logs going back to 1997 burnned to CD.
Large logs is a normal "fact of life" thing and is not specific to SpamFilter ISP. You tend to come up with "tricks" to deal with them. There are also ways to search for something in a log without loading the whole damn thing into notepad. Many 3rd party text editors are much better at handling giant logs also. The Unix / Linux / DBS folks out there have some advantage when it comes to large logs. "Grep" is a great tool that doesn't exit in a Native form for windows. I have seen 3rd party Grep for windows but have never use any of them.
Dan S.
|