Logcheck devel - Jun 2005 - Bug#312376: /etc/logcheck/logcheck.ignore is no longer read

Package: logcheck
Version: 1.2.39
Severity: normal

Since I've upgraded my servers to sarge, I'm getting mail every hour for
stuff that was duly included in /etc/logcheck/logcheck.ignore.  Turns
out that sarge's version no longer reads that file.

If this was a conscious decision, then there should be some warning
about this when upgrading (via debconf of NEWS.Debian).  Also, the
documentation should suggest a location for local rules.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-2
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)

On Tue, 07 Jun 2005, Frederic Briere wrote:
> Since I've upgraded my servers to sarge, I'm getting mail every
hour for
> stuff that was duly included in /etc/logcheck/logcheck.ignore.  Turns
> out that sarge's version no longer reads that file.
> 
> If this was a conscious decision, then there should be some warning
> about this when upgrading (via debconf of NEWS.Debian).  Also, the
> documentation should suggest a location for local rules.
it happened long time ago before the Debian logcheck Team took over.
as it's the first time that this issue pops up since,
i'm not sure if it needs a big fat warning.

the manpage logcheck(8) has a pointer to README.logcheck-database.gz,
which explictly states where and how to setup local-foo rules.

i guess you've overseen it?
thanks for your feedback.

--
maks

Your message dated Wed, 20 Jul 2005 16:34:51 +0200
with message-id <20050720143451.GB20990 at sputnik.stro.at>
and subject line [Logcheck-devel] Bug#312376: /etc/logcheck/logcheck.ignore is
no longer read
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Jun 2005 19:39:40
+0000
>From fbriere at fbriere.net Tue Jun 07 12:39:40 2005
Return-path: <fbriere at fbriere.net>
Received: from smtp.imars.net [64.62.144.114] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DfjvH-0000Nx-00; Tue, 07 Jun 2005 12:39:39 -0700
Received: from toroia.hyrule.dyndns.org (modemcable017.4-201-24.mc.videotron.ca
[24.201.4.17])
	by smtp.imars.net (8.12.11/8.12.11) with ESMTP id j57JdCaM023891
	for <submit at bugs.debian.org>; Tue, 7 Jun 2005 12:39:12 -0700 (PDT)
	(envelope-from fbriere at fbriere.net)
Received: by toroia.hyrule.dyndns.org (Postfix, from userid 1000)
	id 8BE65B7A8; Tue,  7 Jun 2005 15:39:08 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Frederic Briere <fbriere at fbriere.net>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Subject: /etc/logcheck/logcheck.ignore is no longer read
X-Mailer: reportbug 3.12
Date: Tue, 07 Jun 2005 15:39:08 -0400
Message-Id: <20050607193908.8BE65B7A8 at toroia.hyrule.dyndns.org>
Delivered-To: submit at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: logcheck
Version: 1.2.39
Severity: normal

Since I've upgraded my servers to sarge, I'm getting mail every hour for
stuff that was duly included in /etc/logcheck/logcheck.ignore.  Turns
out that sarge's version no longer reads that file.

If this was a conscious decision, then there should be some warning
about this when upgrading (via debconf of NEWS.Debian).  Also, the
documentation should suggest a location for local rules.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-2
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)

---------------------------------------
Received: (at 312376-done) by bugs.debian.org; 20 Jul 2005 14:34:52
+0000
>From max at stro.at Wed Jul 20 07:34:52 2005
Return-path: <max at stro.at>
Received: from baikonur.stro.at [213.239.196.228] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1DvFeu-0004fK-00; Wed, 20 Jul 2005 07:34:52 -0700
Received: from sputnik (stallburg.stro.at [128.131.216.190])
	by baikonur.stro.at (Postfix) with ESMTP id 89E405C013
	for <312376-done at bugs.debian.org>; Wed, 20 Jul 2005 16:34:41 +0200
(CEST)
Received: from max by sputnik with local (Exim 4.52)
	id 1DvFet-00086V-Sv
	for 312376-done at bugs.debian.org; Wed, 20 Jul 2005 16:34:51 +0200
Date: Wed, 20 Jul 2005 16:34:51 +0200
From: maximilian attems <debian at sternwelten.at>
To: 312376-done at bugs.debian.org
Subject: Re: [Logcheck-devel] Bug#312376: /etc/logcheck/logcheck.ignore is no
longer read
Message-ID: <20050720143451.GB20990 at sputnik.stro.at>
References: <20050607193908.8BE65B7A8 at toroia.hyrule.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050607193908.8BE65B7A8 at toroia.hyrule.dyndns.org>
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by Amavis (ClamAV) at stro.at
Delivered-To: 312376-done at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

On Tue, 07 Jun 2005, Frederic Briere wrote:
> Since I've upgraded my servers to sarge, I'm getting mail every
hour for
> stuff that was duly included in /etc/logcheck/logcheck.ignore.  Turns
> out that sarge's version no longer reads that file.
> 
> If this was a conscious decision, then there should be some warning
> about this when upgrading (via debconf of NEWS.Debian).  Also, the
> documentation should suggest a location for local rules.
there is a debconf note logcheck/changes for that change:
it gets displayed at debconf level medium.
you probably choose to ignore that level.

no, we wont set it higher as we don't want to annoy every upgrader.
closing as we didn't get further complaints.
 
--
maks