On Sunday 02 January 2005 03:28, Ed Walker wrote:

We're using syslog-ng, logging about 2million lines/day from a number of email filtering servers. We log to a new file each day.

Right now we've got a perl script that runs just after midnight, and parses each file and dumps the info into a mysql database. For each domain, we have a separate database, for each month, a separate table.

We're interested in moving to direct SQL injection, but are concerned about the possibility of losing logging information if the sql server goes down, or the pipe or injection script die.

What's the most reliable way to do this?

Named pipe? Socket?

Anybody willing to share their configurations and/or scripts?

Thanks-

Ed

_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html

What I do is to also write a log to a file in a comma separated form. If the database or script dies, I can import from the file. No need to keep the file forever, so I keep it for a few days in gzip format and then delete it. If something has gone wrong one should have noticed it by then. Sander