similar to: Bug#388925: logcheck-database: [annoying_notes] Abuse of debconf note(s)

Package: logcheck Version: 1.2.63 Severity: normal Hi, I have just installed logcheck and it works out of the box! thx for that! I just notice that in the /etc/logcheck/ignore.d.workstation/kernel file there is a filter for "[drm] Loading r200 Microcode". COuld you add please the same for the r300. The log message is the same : Apr 6 19:21:14 debian kernel: [drm] Loading R300

Package: logcheck Version: 1.2.69 Severity: normal In the file /etc/logcheck/ignore.d.server/wu-ftpd ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wu-ftpd: PAM-listfile: Refused user [._[:alnum:]-]+ for service wu-ftpd$ should be ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wu-ftpd\[[0-9]{4}\]: PAM-listfile: Refused user [._[:alnum:]-]+ for service wu-ftpd$ There is a number after "wu-ftpd" -- System

Package: logcheck Version: 1.3.3 Severity: normal After upgrading to the latest logcheck, I've noticed that some local rules I have written no longer filter out the logs properly. I've been able to correlate the non-matching to the presence of the '/' (slash) character or '[' (left bracket) in the string that the ".*" pattern ought to match. For instance, I

Package: logcheck Version: 1.3.6 Severity: normal Since logcheck 1.3.6, the report send by mail doesn't support unicode characters : Before : To: logcheck at executor.fruit Subject: Executor.FRUIT 2010-02-01 20:02 ?v?nements li?s ? la s?curit? Auto-Submitted: auto-generated From: logcheck system account <logcheck at executor.fruit> ?v?nements li?s ? la s?curit?

Hi there, My updated Vietnamese translation is attached. :) -------------- next part -------------- A non-text attachment was scrubbed... Name: vi.po Type: application/octet-stream Size: 6969 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20060710/4703d02c/attachment.obj -------------- next part -------------- Regards, Clytie Siddall

Package: logcheck Version: 1.2.63 Severity: minor Tags: patch Hi, There was recently a modification to filter acpid stuffs. But there are still things not filtered by logcheck. When I unplugg, then plug back my battery, I get following notifications: System Events =-=-=-=-=-=-= Nov 8 21:41:31 morpork acpid: received event "ac_adapter AC0 00000080 00000000" Nov 8 21:41:31 morpork

apt-get install svn-buildpackage cat <<_eof >> ~/.svn-buildpackage.conf svn-lintian svn-linda svn-move _eof mkdir logcheck; cd logcheck svn co svn+ssh://svn.debian.org/svn/logcheck/logcheck/trunk cd trunk svn-buildpackage -k<your key ID> -rfakeroot man svn-buildpackage for more. Nice, huh? -- .''`. martin f. krafft <madduck at debian.org> : :' :

Package: xen-api Version: N/A Severity: wishlist Tags: patch l10n Dear Maintainer, Please find attached the french debconf templates translation, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing')

Package: logcheck Version: 1.2.35 Severity: normal I'm getting the following on two different Unstable boxen: ------------------------------------------------------------------------------ Subject: Cron <logcheck at bandit-hall> if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi

Package: logcheck-database Version: 1.2.39 Severity: wishlist Hi, I'd like to add the following rule to /etc/logcheck/violations.ignore.d/logcheck-postfix : ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd?\[[0-9]+\]: NOQUEUE: reject: RCPT from [._[:alnum:]-]+\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\]: 554 <[._[:alnum:]-]+\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\]>:

Package: logcheck-database Version: 1.2.25 Severity: normal postfix/smtpd\[[0-9]+\]: lost connection after (CONNECT|DATA|RCPT|RSET|EHLO|HELO|MAIL) from Please include the above line in the ignore.d/server/postfix file. That catches messages that occur very often on busy Postfix servers. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable')

Package: logcheck Version: 1.2.47 Severity: wishlist I'm running logcheck with an extended set of regular expressions on a desktop system. The CPU load of this system is normally very low, around 3%-5%. When logcheck starts scanning the logs, the CPU usage increases to 100% for several minutes and working on the system becomes difficult. I would therefore be very happy about if a

Package: logcheck-database Version: 1.2.54 Severity: normal Tags: patch Logcheck fails to ignore certain lines generated by OpenVPN; the attached patch fixes several regular expressions: * OpenVPN does not print the full path to ifconfig or route (at least here) * The interface name can also contain dots and does not always start with "tun" * The startup messages now gets suppressed

Package: logcheck-database Version: 1.2.43a Severity: minor Since last weekend's upgrade of logcheck-database from 1.2.42 to 1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of the form Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286 Could you please edit the second pattern in

Package: logcheck-database Version: 1.2.54 Severity: normal The included filters for cyrus (/etc/logcheck/ignore.d.server/cyrus) are very minimal. The cyrus-imapd-2.2 has a more extensive ruleset (there's a /etc/logcheck/ignore.d.server/cyrus2_2 file in that package). Please copy over the filters from cyrus-imapd-2.2. I'm running logcheck on a loghost, which doesn't run cyrus

Package: logcheck Version: 1.2.56 Followup-For: Bug #429384 I get the following message in my e-mail from cron: Cron <logcheck at entercom> if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi /usr/sbin/logcheck: line 645: mktemp: command not found /usr/sbin/logcheck: line 646: mktemp: command not found rm: too few arguments Try `rm --help' for more information.

hello, the debconf configuration of logcheck was removed since woody release: as logcheck's user base is targeting server admins, we don't see the need of a debconf based question regarding the frequency of logcheck. beside once per day is a good default. a note was added to documentation README.Debian that this value may be changed in /etc/cron.d/logcheck. so these bugreports will be

Package: logcheck-database Version: 1.2.49 Severity: normal My logcheck configuration is quite a default one, ignore level server. i found the "session opened" and "session closed" ignore lines in ignore.d.server/logcheck. but i still get those lines in the logcheck mails: Nov 12 17:17:01 server06 CRON[32741]: (pam_unix) session opened for user root by (uid=0) Nov 12

Package: logcheck-database Version: 1.2.54 Severity: normal Hello, it seems crontab reports it's whole path in syslog : May 6 16:00:03 eckmul /usr/bin/crontab[9722]: (root) LIST (nobody) I don't have other messages from it in my logs, so I can't comment on the other lines in /etc/logcheck/ignore.d.server/cron , but I had to modify the LIST one with /usr/bin/crontab Thanks, --

Package: logcheck-database Version: 1.2.51 Severity: normal Messages such as these are no longer being filtered by logcheck ('hostname' used to replace actual hostname; 'hostname.com' used to replace actual domain): Dec 23 12:02:58 hostname postfix/lmtp[5047]: 38BE4C21ED: to=<root at hostname.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.1, delays=2/0.16/0.05/1.8,