heya, on which note just wanted to say thanks for the effort of writing that up. I had a quick look at it the other day and it helped clarify a couple of things, namely how you piped things straight into swatch (which is a nice trick). regards, -------------------- Benjamin Smee Technical Specialist Optus Business Operations (NAC) "YES" OPTUS ben.smee@optus.net.au Tel: +61-2-93420091 Fax: +61-2-93420998 Perilous to all of us are the devices of an art deeper than we possess ourselves. -- Gandalf the White
-----Original Message----- From: Nate Campi [mailto:nate@campin.net] Sent: Saturday, 24 November 2001 8:01 AM To: syslog-ng@lists.balabit.hu Subject: [syslog-ng]syslog-ng loghost project documentation
I've documented just about every part of my syslog-ng setup at work, and place it at http://www.campin.net/newlogcheck.html. It > covers the whole deal, from reporting with custom log scanners, swatch, archiving to files and to a database, and more.
This may save others time when they are starting out on their projects. This is a work in progress, but I'm sure it could be useful now. -- Nate Campi http://www.campin.net GnuPG key: 0xC17AEF79 Key fingerprint = BF12 722F 8799 E614 33CC FAB7 5A90 C464 C17A EF79
Your mantra for today is: Don't let data from the network near a shell. Bad things happen. -- Randall Schwartz
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/sysl> og-ng