I've put together a patch against qmail-scanner 1.16 that logs the virus reports to a MySQL database. It leaves the file system logging in place so you actually end up with two sets logs. I suppose if you felt comfortable with the SQL logging, you could remove the file system logging.
I have been running this patch in a production environment for the last few weeks with no problems. I've also written a quick and dirty reporting tool similar to QSS. If you don't like the idea of logging direct to SQL, I also have an import script that parses the log file and imports to SQL. I have it running on another system with no problems. Just setup a cron job to run every 5 minutes or whatever you desire. You'll find the import.php script included with the reporting tool. It's not without it's problems. The qmail-scanner virus log is tab delimited. Every once and a while I'd run into tabs in the subject or somewhere that would prevent the record from importing correctly. Logging direct to SQL from qmail-scanner seems to take care of this problem since the log file doesn't have to be parsed. More information at: http://www.theboenings.com/qmail-scanner/ ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
