similar to: Bug#644583: Extra patch for smtpd_client_port_logging

Package: logcheck Version: 1.3.14 Severity: normal Tags: patch Hi I don't want the logcheck email alias because I configure logcheck to send email to a different address, but it keeps getting re-added on upgrades. I've prepared a patch to only add the alias on install, not on upgrades, but I've noticed some small issues with the rest of the postinst (tests which could

Package: logcheck Version: 1.3.15 Severity: minor Tags: patch Hi, Got this log from time to time in System Events: Oct 23 13:48:16 pig2 named[28880]: success resolving '26.0/25.218.183.203.in-addr.arpa/PTR' (in '0/25.218.183.203.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets Changing the regexp for the "(in '...'?)"

Processing commands for control at bugs.debian.org: > submitter 192827 Jos? Luis Gonz?lez <jlgonzal at ya.com> Bug #192827 [xdiskusage] xdiskusage: Printing doesn't manage non-ASCII characters Changed Bug submitter to 'Jos? Luis Gonz?lez <jlgonzal at ya.com>' from 'Jos?? Luis Gonz??lez <jlgonzal at ya.com>' > submitter 208308 R?diger Kuhlmann

fwd'ing to klibc malinglist. ----- Forwarded message from Lo?c Minier <lool at dooz.org> ----- Date: Wed, 16 Mar 2011 23:34:51 +0100 From: Lo?c Minier <lool at dooz.org> To: Debian Bug Tracking System <submit at bugs.debian.org> Subject: Bug#618616: arm build failure with latest binutils - usr/klibc/syscalls/_exit.S:29: Error: .size expression does not evaluate to a

Package: logcheck Version: 1.2.54 When Postfix is configured to listen on port tcp/587 by uncommenting the "submission" line in the postfix master.cf, logcheck does not ignore the anvil statistics log entries - attached is a patch from the current SVN trunk. -------------- next part -------------- A non-text attachment was scrubbed... Name: logcheck_1531.diff Type: text/x-patch Size:

Package: logcheck Version: 1.3.13 Severity: normal Hi, at present my logcheck is into 33 minutes of cpu time for running the ignore/innd rule, when the innd package is not installed. If running logcheck against only locally created logfiles, there should be a configuration option to only run logcheck against installed (or non-purged) packages. -- System Information: Debian Release: squeeze/sid

commit 81496d0cf7b161bf981d51f0b96f860d68f3f6e3 Author: Micah Anderson <micah at debian.org> Date: Fri Aug 24 17:51:31 2007 -0400 Enable alternate temporary directory to be set in the configuration file On servers where the logfiles are very large and grow quickly, the logcheck processes may run into space issues in /tmp resulting in the email such as the following to be

Package: logcheck Version: 1.3.14 Severity: normal Tags: patch I keep getting these messages logged, when under high load. This patch should clean that up. commit 72661acccafa519fcb48a6a756e5c35d96e7511d Author: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn at axis.com> Date: Fri Jan 27 16:08:33 2012 +0100 Workaround for error: /usr/sbin/logcheck: line 100: kill: (31667)

Hello I try to execute logcheck from a php page. So I have create a php page with a button which allow to run logcheck like this : /usr/sbin/logcheck -o > /var/log/logcheck (I want to put the result in a file logcheck, that's why I use the option -o) I have put www-data in the groupe adm : "adduser www-data adm" And after if I run logcheck like this for exemple:

Hello, I'm having this error: Warning: If you are seeing this message, your log files may not have been checked! Details: Could not run logtail or save output Check temporary directory: /tmp/logcheck.EIX3jp declare -x HOME="/var/lib/logcheck" declare -x LANG="en_US" declare -x LANGUAGE="en_US:en_GB:en" declare -x LOGNAME="logcheck" declare -x

Package: logcheck Version: 1.3.13 Severity: normal Various files under ignore.d.* use "[0-9.]{7,15}" to match an IPv4 address, e.g., a connection to rsyncd. However, this does not match IPv6 addresses, causing spurious reports. A better regexp might be something like: ([0-9.]{7,15}|[0-9a-f:]{2,39}) -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990,

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.

The entry is probably not igored because of the word deny in your path . You might better set your rule in violation.ignore.d/ directory. At 13:00 09/01/2006, you wrote: >Send Logcheck-users mailing list submissions to > logcheck-users@lists.alioth.debian.org > >To subscribe or unsubscribe via the World Wide Web, visit >

Hi guys, now that violations.d/logcheck is empty, violations.ignore.d/logcheck-* are useless and many messages that were previously elevated and filtered there now turn up as system events. Thus, I went ahead and merged violations.ignore.d/logcheck-* into ignore.d.*/* in the viol-merge branch. http://git.debian.org/?p=logcheck/logcheck.git;a=shortlog;h=refs/heads/viol-merge Unless I hear

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 Version: 1.3.14 Severity: normal I added a local.rules file to ignore.d.server and then ran logcheck. The file was not used during the run. Renaming it to local-rules got the file used during the next run. Fix: periods should be allowed in filenames, or the fact that they are forbidden expressly documented inteh logcheck README. Thanks Nils -- System Information: Debian

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

Hello, list! I can't run logcheck. This is the first time my system has not let me run something, any way I try. I am member of sudo group. I run this sudo -u logcheck logcheck -o -t and get Sorry, user [user] is not allowed to execute '/usr/sbin/logcheck -o -t' as logcheck on [machine]. If I try su -s /bin/bash -c "/usr/sbin/logcheck -o -t" logcheck I get

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