similar to: (fwd) Bug#319169: logcheck: chokes on log files whose names contain spaces

hey todd, looked again at that return value check merge: @@ -557,7 +584,8 @@ # the same lines) and reduce CPU and memory usage afterwards. debug "Sorting logs" $SORT -m $TMPDIR/logoutput/* | uniq | sed -e 's/ *$//' \ - > $TMPDIR/logoutput-sorted + > $TMPDIR/logoutput-sorted \ + ||error "Could not output to $TMPDIR/logoutput-sorted Disk Full?" i guess

I'm running logcheck on a machine hosting a bunch of virtual machines using vserver, so I'd like to expand shell wildcards in the "logcheck.logfiles" file. So instead of entering /var/lib/vservers/v1/var/log/syslog /var/lib/vservers/v2/var/log/syslog /var/lib/vservers/v2/var/log/syslog I can enter /var/lib/vservers/*/var/log/syslog which gets expanded to the same thing as

On Tue, 2005-05-03 at 07:20 +0000, CVS User maks-guest wrote: > Modified Files: > logcheck.sgml > Log Message: > > minor addition describe 3 layers. > remove the url tag not recognized by docbook2man. > + > + <para>The reported messages are sorted in three different layers. > + The system events verbosity is governed by aboves level choice. > + The

hello russel, On Mon, 10 Jun 2002, russell at coker.com.au wrote: .. > I would like to be able to have different parts of the report sent to > different people. For example if I install a new daemon on a server > I want the messages for that daemon going only to me (not the entire > admin team) until I get it working properly. Otherwise excessive > spurious messages lead

Package: logcheck Version: 1.2.41 Problem: Logcheck try to detect if log file have been rotate or not by file size way. Possible attack: - current log file (sizeA) - run logcheck, (logcheck/logtail put inode in offsetfile), offset=sizeA - [attacker run attack 1] - run logrotate - [attacker run attack 2] - run logcheck may don't detect the rotation and don't check the log for attack 1

Package: logcheck Version: 1.3.13 Severity: minor Tags: patch In Lenny it was possible to use wildcards in logcheck.logfiles. For example, I used: /var/log/HOSTS/*/*.log root at durer:~# su -s /bin/bash -c "bash -x /usr/sbin/logcheck" logcheck <cut> + read file + logoutput '/var/log/HOSTS/*/*.log' + file='/var/log/HOSTS/*/*.log' + debug 'logoutput called

On Sat, 15 May 2004, CVS User ttroxell wrote: > if [ -f /etc/logcheck/header.txt ] ; then > - $CAT /etc/logcheck/header.txt >> $TMPDIR/report > + $CAT /etc/logcheck/header.txt >> $TMPDIR/report \ > + || error "Could not append header to $TMPDIR/report Disk full?" > fi > } > > @@ -152,7 +157,8 @@ > # Add a footer

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 wanted to work on #195935, but found a less than funny issue, easy to reproduce: * remove some lines in front of your logfile * invoke logcheck you'll get a big email with all not matching lines from that log. not setting that to high priority because you are getting also the newer loglines. don't know if i find time that weekend. wanted to document it anyways. a++

On Wed, 05 Jan 2005, CVS User ttroxell wrote: > @@ -70,6 +70,10 @@ > chown logcheck /var/lock/logcheck > /dev/null 2>&1 || true > fi > > + # fix for #284788 > + # update timestamp on cron > + touch /etc/cron.d/logcheck || true > + > ;; > > abort-upgrade|abort-remove|abort-deconfigure) on a box with a broken coreutils install

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

hello everyone, thanks to todd 1.2.21 is out :) every release getting better, i would like to get consensus on these "important" bugs: #252078 logtail: should depend on perl >= 5.8 sarge as any other modern linux distro use perl 5.8.x, it's even inside of its base. backports are under the peril of its author if no one voices up, i'll close that bug in the next days.

A non-text attachment was scrubbed... Name: parse_logcheck Type: application/octet-stream Size: 3860 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20040901/b1727d89/attachment.obj

Package: logcheck Version: 1.1.1-13.1woody1 Severity: important logcheck line 56 uses "TMPDIR=$(mktemp -d -p ..." but mktemp from woody doesn't accept -p option Cheers, Chris -- System Information Debian Release: 3.0 Kernel Version: Linux ethlife-a 2.4.26-vs1.27 #4 SMP Mit Apr 28 15:20:15 MEST 2004 i686 unknown Versions of the packages logcheck depends on: ii cron

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

Your message dated Thu, 08 Sep 2011 14:48:50 +0000 with message-id <E1R1fuM-0008SF-9f at franck.debian.org> and subject line Bug#639839: fixed in logcheck 1.3.14 has caused the Debian Bug report #639839, regarding amavisd-new: logcheck "Passed: CLEAN|SPAM" doesn't work because mail-id can contain "-" to be marked as done. This means that you claim that the problem

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')

----- Forwarded message from General Stone <generalstone at gmx.net> ----- X-Original-To: maks at sternwelten.at Date: Mon, 2 Jan 2006 14:59:03 +0100 From: General Stone <generalstone at gmx.net> To: maximilian attems <maks at sternwelten.at> Subject: Re: [Logcheck-devel] Bug#344832: correct subject header On Mon, Jan 02, 2006 at 02:09:48PM +0100, maximilian attems wrote: >

Package: logcheck Version: 1.2.20a Severity: important Since logcheck changed to run as user logcheck, the error mails of the cron daemon end up in /var/mail/logcheck where nobody reads them. Mails for logcheck should be aliased to root like all the other mails of system accounts. I was searching for a long time what was wrong with my logcheck not delivering any mails. The lock directory was

Package: logcheck-database Version: 1.2.40 Severity: wishlist Hi, Please duplicate the imap-login related lines and change them to filter out the equivalent messages emitted by pop3-login. regards Andrew -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: