[leafnode-list] Re: leafnode creating multi-megabyte log files )-:
Robert Grimm
lists at news.robgri.de
Thu May 19 10:58:39 CEST 2011
Arthur Marsh <arthur.marsh at internode.on.net> wrote:
[...]
> I'm also running logcheck and it is spending hours processing log files
> of the form:
> May 16 14:05:59 victoria fetchnews[24378]: gmane.test: killed 3423
> (<el9g92$uv5$
> 1 at sea.gmane.org>), too old (1621 > 15) days
> May 16 14:05:59 victoria fetchnews[24378]: gmane.test: killed 3424
> (<ela7ta$7g0$
> 1 at sea.gmane.org>), too old (1621 > 15) days
Maybe there is a problem with commits
71894c6e96d7afad506776bfe8156a0848ab4f4c
resp.
6f5b52277e4a0cfcd6b85eb714679a0d537d24a3
?
Will investigate when I find the time.
> Is there any straightforward way to stop leafnode writing such log files
> to begin with?
For the default syslog daemon (rsyslog) in Debian the following changes
should work:
#v+
--- /etc/rsyslog.conf.orig 2011-05-19 10:19:51.808359097 +0200
+++ /etc/rsyslog.conf 2011-05-19 10:21:43.400348458 +0200
@@ -49,6 +49,8 @@
###############
#### RULES ####
###############
+#Discard messages from the news system with priority info.
+news.=info ~
#
# First some standard log files. Log by facility.
#v-
e.g add the line
news.=info ~
at the top of your rules section in /etc/rsyslog.conf.
Don't forget /etc/init.d/rsyslog restart.
Rob
--
If you didn't have most of your friends,
you wouldn't have most of your problems.
More information about the leafnode-list
mailing list