Displaying 20 results from an estimated 1000 matches similar to: "Bug#287184: logcheck overwriting ownership/permissions of /etc/logcheck/* on upgrades"
2004 Dec 20
3
Bug#286532: dnsmasq: misses message for DHCPINFORM due to 283331 fix
Package: logcheck-database
Version: 1.2.32
Severity: normal
Tags: patch
The fix for 283331 exposed a bug in the dnsmasq rules. The rule was
looking for DHCPINFO, but the actual message is DHCPINFORM. Prior to
the 283331 fix, the old rule worked, because the "[()[:alnum:]]+" part
of the rule matched the "RM" at the end of DHCPINFORM.
-- System Information:
Debian Release:
2004 Dec 21
3
Bug#286747: logcheck-database: ignore rules for USB headset
Package: logcheck-database
Version: 1.2.32
Severity: wishlist
Ignore rules to supress messages generated from pugging in, and
then removing, a USB headset (one speaker).
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: drivers\/usb\/class\/audio\.c: v1.0.0:USB Audio Class driver$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: usbaudio: assuming that a stereo channel connected directly to a mixer is
2005 Jan 20
2
Bug#291395: logcheck-database: Rules dirs are setuid, they should be setgid
Package: logcheck-database
Version: 1.2.33
Severity: normal
I just installed 1.2.33, and it made my rules dirs setuid, not setgid...
- Marc
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of
2004 Oct 21
3
Bug#277636: logcheck-database: support for dnsmasq
Package: logcheck-database
Version: 1.2.28
Severity: wishlist
Could you add support for dnsmasq for the server profile?
This is the standard dnsmasq output.
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: read /etc/hosts - [[:digit:]]+ addresses$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: reading /etc/resolv.conf$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2005 Mar 06
3
Bug#298291: logcheck-database: Printer out-of-paper reported
Package: logcheck-database
Version: 1.2.34
Severity: minor
I have parallel port attached printer and kernel reports whenever
printer is out of paper:
Mar 6 12:38:50 host kernel: lp0 out of paper
However, this is not a situation that should be reported by default
(IMHO) by logcheck sending report email. Thus I propose adding
following line to ignore.d.workstation/logcheck (possibly to .server
2004 Nov 21
2
Bug#282378: logcheck-database: messages from USB joystick use
Package: logcheck-database
Version: 1.2.31
Severity: wishlist
The following is reported by logcheck when inserting a USB joystick for
the first time (workstation), none of which (I assume) I need to be
informed of.
Nov 21 17:50:08 localhost kernel: ohci_hcd 0000:00:01.2: wakeup
Nov 21 17:50:08 localhost kernel: usb 1-1: new low speed USB device using address 2
Nov 21 17:50:10 localhost kernel:
2005 Feb 16
3
Bug#295560: logcheck: Please include filename when reporting "invalid regular expression"
Package: logcheck
Version: 1.2.34
Severity: wishlist
I have a couple of home-made logcheck ignore files, and happened to
have one unescaped (and unmatched) `(' in one of the filter
lines. Because of this, cron sent a mail with the body "grep: Invalid
regular expression" - the subject is the command in the "2 * * * *"
line in /etc/cron.d/logcheck, of course.
It would be
2005 Apr 26
3
Bug#306388: add ignore line for udhcpd
Package: logcheck-database
Severity: wishlist
Hi,
the following two lines should be added either to ignore.d.server/dhcp or
ignore.d.server/udhcp to ignore messages from udhcpd (other lines may be
necessary)
# udhcpd support
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ udhcpd\[[0-9]+\]: sending OFFER of [.0-9]+
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ udhcpd\[[0-9]+\]: sending ACK to [.0-9]+
filippo
2004 May 28
2
Bug#251364: logcheck: preinst has bashism, fails with dash and LANG != C
Package: logcheck
Version: 1.2.20a
Severity: serious
Tags: patch
On a system where sh points to dash and LANG=es_ES, I get this:
# apt-get -y --reinstall install logcheck
Leyendo lista de paquetes... 0%
Leyendo lista de paquetes... 0%
Leyendo lista de paquetes... 23%
Leyendo lista de paquetes... Hecho
Creando ?rbol de dependencias... 0%
Creando ?rbol de dependencias... 0%
Creando ?rbol de
2005 Jan 11
2
Bug#289801: Logtail should output error messages to stderr, not stdout
Package: logtail
Version: 1.2.33
Severity: normal
Hi...
Logtail should not output error messages to standard output, since this
violates the principle of least surprise.
In particular, my application was broken by the semantics of logtail changing
in version 1.2.21 (when you added switches for the default arguments to
logtail). I think this was a bad move -- you broke an interface used by
2004 Jul 15
5
Bug#259603: logcheck-database: postfix/lmtp rules do not match some configurations
package: logcheck-database
version: 1.2.23
severity: wishlist
The current regexp's for postfix/lmtp..
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/lmtp\[[0-9]+\]: [0-9A-F]:
to=<[^[:space:]]+>, orig_to=<[^[:space:]]+>, relay=[^[:space:]]+\],
delay=[0-9]+ status=sent \(250 2\.1\.5 Ok\)$
..doesn't catch these messages:
Jul 15 17:15:16 lorien postfix/lmtp[17151]: C1170480008B:
2005 Mar 28
1
logcheck errors after logrotate runs
--nextPart2699335.H7BBWTdPIb
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hello :)
After upgrading recently from Woody to Sarge (which went fairly well) I now=
=20
have trouble with logcheck. I have been unable to track down a solution.
Logcheck runs perfectly through the week until Sunday when logrotate does
2005 Sep 15
2
Bug#328632: Please include README.logcheck-database.gz
Package: logcheck
Version: 1.2.41
Severity: minor
man (8) logcheck says:
For hints on how to maintain rules, see README.logcheck-database.gz,
but this file is not included in /usr/share/doc/logcheck.
micah
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel:
2004 Jun 04
2
Bug#252597: logcheck: user logchecks mails should be delivered to root
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
2004 Aug 31
1
Bug#269318: logcheck: /etc/logcheck/ignore.d.server (add spamassassin)
Package: logcheck
Version: 1.2.26
Severity: wishlist
Please add ignore for Spamassasin's "check" messages like:
Aug 16 19:27:54 ns spamd[23853]: checking message <20040816150710.86ADA708A8 at smtp-out.hotpop.com> for nobody:65534.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.26.20040601
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL
2004 May 26
5
Bug#251046: logcheck: invalid mktemp -p option
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
2005 Jan 12
3
Bug#290195: violations.d/sudo and violations.ignore.d/logcheck-sudo missing sudo log entries
Package: logcheck
Version: 1.2.32
Severity: normal
It seems when someone runs a sudo command on my system, logcheck misses
it.
The second line of /etc/logcheck/violations.d/sudo matches them, but
the /etc/logcheck/violations.ignore.d/logcheck-sudo kills them.
Furthermore, when users run commands like '$ sudo rm *' in a directory
with lots of files, we reports with lines like:
Jan 13
2004 May 15
1
Re: [Logcheck-commits] CVS logcheck/src
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
2005 Aug 31
3
Bug#325801: logcheck: new regex to filter imap "Moved xxx bytes of new mail" messages
Package: logcheck
Version: 1.2.41
Severity: wishlist
Hi folks, thanks for your work maintaining logcheck, it works well.
When my users read their mail using imap (usually via squirrelmail,
not sure about other clients) I get a message like this in the log:
Aug 22 21:03:32 phoenix imapd[6551]: Moved 11323 bytes of new mail to /home/winky/mail/mbox from /var/spool/mail/winky host= localhost
2005 Apr 07
1
Bug#303661: logcheck-database: openntpd rules
Package: logcheck-database
Version: 1.2.37
Severity: normal
Hello again,
openntpd gives messages like these failry often:
Apr 7 14:25:55 terminus ntpd[673]: peer 204.17.42.202 now invalid
Apr 7 14:26:10 terminus ntpd[673]: peer 204.17.42.202 now valid
I am not sure if this is something that an admin may find relevant but they happen fairly often and they do not offer a lot of info
for me.