Your message dated Sat, 30 Sep 2006 10:50:16 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390290: leafnode: should filter "clamping maxage for
[^[:space:]]+ to global expire" in logcheck
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)
--- Begin Message ---
Package: leafnode
Version: 1.11.5-3
Severity: wishlist
In my logcheck filters, "clamping maxage for
<newsgroup-name> to global expire" is not set to ignore and I get a
large number of such messages in logcheck from fetchnews.
Could such a filter be added? I would still like to see the *non
default* expire times in the log, so perhaps 2 rules should be added,
one for "global expire" conditions and another for expires set
specifically for a particular newsgroup.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Versions of packages leafnode depends on:
ii debconf [debconf-2.0] 1.5.5 Debian configuration management sy
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi
ii logrotate 3.7.1-3 Log rotation utility
ii netbase 4.26 Basic TCP/IP networking system
ii tcpd 7.6.dbs-11 Wietse Venema's TCP wrapper utilit
leafnode recommends no packages.
-- debconf information:
* leafnode/update-groups: false
leafnode/tcpd: true
leafnode/ppp:
* leafnode/network: permanent
leafnode/purge: false
* leafnode/server: news-server.bigpond.net.au
--- End Message ---
--- Begin Message ---
On Sat, Sep 30, 2006 at 06:43:39PM +0930, Arthur Marsh wrote:
> In my logcheck filters, "clamping maxage for
> <newsgroup-name> to global expire" is not set to ignore and I get a
> large number of such messages in logcheck from fetchnews.
These warnings are deliberately left visible since they report that the
maxage set for the group is being ignored, indicating that the
configurtion is not doing what one might expect from reading it - the
message is a warning that something might be wrong. I would suggest
either adjusting your configuration so that no clamping is needed or
adding the rule locally.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
--- End Message ---
