Re: Debian Sarge Logcheck Query

2004-02-16 Thread Peter A. Cole
- Original Message - From: "Brian Brazil" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 17, 2004 5:47 AM Subject: Re: Debian Sarge Logcheck Query > Just a thought - if you don't get any messages how do you know that your > ma

Re: Debian Sarge Logcheck Query

2004-02-16 Thread Brian Brazil
On Mon, Feb 16, 2004 at 09:31:11PM +1000, Peter A. Cole wrote: > In fact logcheck didn't even send an email a minute ago when I check, which > is how I want except for reboots and unexpected events. Just a thought - if you don't get any messages how do you know that your machine hasn't been compro

Re: Debian Sarge Logcheck Query

2004-02-16 Thread Peter A. Cole
- Original Message - From: "Brian Brazil" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 16, 2004 9:19 PM Subject: Re: Debian Sarge Logcheck Query > On Mon, Feb 16, 2004 at 09:02:18PM +1000, Peter A. Cole wrote: > > I'm using

Re: Debian Sarge Logcheck Query

2004-02-16 Thread Brian Brazil
On Mon, Feb 16, 2004 at 09:02:18PM +1000, Peter A. Cole wrote: > I'm using logcheck to get notifications on my Debian Sarge box, but I would > really like to get rid of a few extra messages that can be ignored. The > entries I want to ignore are: > > Feb 16 20:49:38 jake in.qpopper[2843]: connect

Debian Sarge Logcheck Query

2004-02-16 Thread Peter A. Cole
Hi all, I'm using logcheck to get notifications on my Debian Sarge box, but I would really like to get rid of a few extra messages that can be ignored. The entries I want to ignore are: Feb 16 20:49:38 jake in.qpopper[2843]: connect from 10.200.50.152 Feb 16 20:49:38 jake in.qpopper[2843]: (v4.0.