Red Hat Logwatch

[Chris Stankaitis]

Hi all,

I have been using nagios for quite a long while now, but there are a 
couple of loose ends in my implementation that I am trying to tie up.  I 
do SSH checks with Nagios using the check_ssh plugin, and each of of 
these SSH checks show up as

**Unmatched Entries**
Connection from 10.0.0.XX port 33309
Enabling compatibility mode for protocol 2.0
Connection from 10.0.0.XX port 33479
Enabling compatibility mode for protocol 2.0
Connection from 10.0.0.XX port 33612
Enabling compatibility mode for protocol 2.0
Connection from 10.0.0.XX port 33792
Enabling compatibility mode for protocol 2.0


in my daily logwatch creating *pages* of crap to have to filter through, 
has anyone hacked up the logwatch scripts to ignore their nagios server 
IP?? if so could you perhaps send me a patch or point me down the right 
road to making the code changes to filter out this info, or otherwise 
condense it into a manageable size... I.E.

**Unmatched Entries**
Connection from 10.0.0.XX port 33309 ... 705 times

or something like that.


-- 
Chris



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null