Hi David, thanks for your reply. <[EMAIL PROTECTED]> wrote:
>My impression from reading that site is that the monitor scripts reference >are proprietary scripts written by Intrustion Inc., provided as part of the >SecureNet Sensor product they sell. Yes thats a possibility >For a general purpose monitor script you'd probably want something that >parses syslog output. There is a syslog.monitor included with mon that >serves as a syslogd replacement, but I've never personally used it. (I >didn't like the 'must replace syslogd' requirement..) Hm, i've read the README, but it isn't so self-explaining... And if you say there's a must to replace syslogd, i don't like it too. I found another one (monlogerrtrapd) but i couldn't figure out how to configure it right. Can someone send me an example or a howto? Also the patterns file.. And how can i trigger from the mon.cf the monlogerrtrapd? > >I have a similar tool which watches the syslog log files and pattern >matches on the output, generating mon traps as necessary. I could probably >add it to the mon CVS area if anyone is interested in using it... Yes that would be cool. -Michael ---------------------------------------------------------------- Service provided by http://www.chat-net.ch _______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
