Displaying 20 results from an estimated 3000 matches similar to: "Bug#429384: logcheck should depend on mktemp package"
2007 Jun 26
0
Bug#429384: logcheck: Logcheck depends on mktemp
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.
2007 Feb 28
0
Bug#330220: Permissions of /var/lock/logcheck not conducive to logcheck user writing to it
Package: logcheck
Version: 1.2.54
Followup-For: Bug #330220
root at ns2:/# ls -l /var/lock/
total 4
drwxr-xr-x 2 root root 4096 2007-01-30 15:40 logcheck
I think chmod 775 on that file would fix this problem...
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked
2006 Dec 02
2
Bug#401259: logcheck: logcheck needs to override locale for grep
Package: logcheck
Version: 1.2.51
Severity: normal
Logcheck has an implicit assumption that the default locale should be
used by grep when processing log files. However, that's not always
the case. For example, I use the locale "en_US.UTF-8", and
consequently grep assumes that its inputs are encoded as UTF-8. But
the log files appear to be encoded as ISO 8859-1, which means that
2006 Apr 28
1
Bug#365121: logcheck: Fails to ignore certain pattern
Package: logcheck
Version: 1.2.43a
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have messages like these in my logs:
Apr 27 10:05:49 localhost smartd[9357]: Device: /dev/hda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 58 to 57
Apr 27 10:05:49 localhost smartd[9357]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 58 to 57
2007 Oct 06
1
Bug#445537: logcheck: Kein Deutsch in config Dateien bitte
Package: logcheck
Version: 1.2.62
Severity: minor
# Send the results as attachment or not.
# 0=not as attachment; 1=as attachment
# Default ist 0
^^^
MAILASATTACH=0
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-rc8+cfs (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8,
2006 Feb 21
2
Bug#353815: logcheck: Ignore Pocket PC/synce/USB messages, please
Package: logcheck
Version: 1.2.42
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Here are some more messages that can be safely ignored:
localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
localhost kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for PocketPC PDA
localhost kernel: drivers/usb/serial/ipaq.c: USB PocketPC PDA driver
2007 Mar 04
0
Bug#413364: logcheck ignores cron rules for "session closed" and "session opened"
Package: logcheck
Version: 1.2.54
Severity: normal
In the file ignore.d.paranoid/cron there are the rules
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ CRON\[[0-9]+\]: \(pam_[[:alnum:]]+\) session opened for user [[:alnum:]-]+ by \(uid=[0-9]+\)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ CRON\[[0-9]+\]: \(pam_[[:alnum:]]+\) session closed for user [[:alnum:]-]+$
to ignore lines like
10:17:01 at 04-03-2007 tooar
2007 Jun 11
0
Bug#428428: patch for cron ignore rule
Package: logcheck
Version: 1.2.54
Severity: normal
Tags: patch
On my system, this ignore rule needs /usr/bin/ in front of the cron command, or the rule fails to match.
hostname:/etc/logcheck/ignore.d.server# diff cron cron.old
1c1
< ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ (/usr/bin/)?crontab\[[0-9]+\]: \([[:alnum:]-]+\) LIST \([[:alnum:]-]+\)$
---
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2004 May 21
2
Bug#247360: logcheck: Where's NEWS.Debian?
Package: logcheck
Version: 1.2.20a
Severity: normal
Followup-For: Bug #247360
I can't find NEWS.Debian in the package.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R
Versions of packages logcheck depends on:
ii adduser
2006 Mar 29
2
Bug#359878: logcheck: extend exim rules to cope with multiple recipients
Package: logcheck
Version: 1.2.43a
Severity: normal
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.6.10
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8
Versions of packages logcheck depends on:
ii adduser 3.77 Add and remove
2006 May 01
2
Bug#365565: logcheck: improve description of FQDN option
Package: logcheck
Version: 1.2.43a
Severity: wishlist
The conf file currently says
# Should the hostname of the generated mails be fully qualified?
FQDN=1
I suggest rewording that to
# Should the hostname in the subject of the generated mails be fully qualified?
FQDN=1
The current wording led me to believe that the sender, and perhaps
recipient (if otherwise unqualified) of the emails generated
2006 Oct 06
0
Bug#391458: logcheck: Please provide a way to configure niceness of log scanning process
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
2006 Mar 07
0
Bug#355649: logcheck: ntp 'adjusting local clock' only matches positive corrections
Package: logcheck
Version: 1.2.43a
Severity: minor
/etc/logcheck/ignore.d.server/ntp contains:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjusting local clock by [.0-9]+s$
However, this will not match negative corrections such as:
System Events
=-=-=-=-=-=-=
Mar 5 01:44:55 billchase ntpd[6171]: adjusting local clock by -0.190112s
Mar 5 01:55:20 billchase ntpd[6171]: adjusting local
2006 Feb 06
1
Bug#351669: logcheck: [manual] the sudo(1) is missing from EXAMPLES
Package: logcheck
Version: 1.2.35
Severity: minor
Current manual reads:
EXAMPLES
logcheck can be invoked directly thanks to su(8) or sudo(8), which
change the user ID:
logcheck -o -t Check the logfiles without updating the offset. Print
everything to STDOUT
I believe this shuold be formatted as:
EXAMPLES
logcheck can be invoked directly thanks
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
2007 Aug 23
0
Bug#439207: postgrey: multiple recipients generates slightly different whitelisted message
Package: logcheck
Version: 1.2.57
Severity: normal
Tags: patch
In ignore.d.server/postgrey,
change:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: action=.+, reason=.+, (delay=.+, )?client_name=.+,
client_address=.+, sender=.*, recipient=.+
to:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: ([0-9A-F]+: )?action=.+, reason=.+, (delay=.+, )?client_name=.+,
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
2009 Sep 15
0
Bug#546771: logcheck fails to locate lockfile-progs at non standart location
Package: logcheck
Version: 1.2.69
Severity: normal
Tags: patch
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30.4-vs2.3.0.36.14-pre4 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages logcheck depends
2005 Feb 19
2
Bug#296017: logcheck: ignore.d.server pure-ftpd user with trailing whitespace
Package: logcheck
Version: 1.2.34
Severity: normal
the patterns for pure-ftpd in ignore.d.server are not matching a user
with a trailing whitespace. here a some examples:
Feb 18 13:02:33 web1 pure-ftpd: (stupid-pure-ftpd @84.56.131.73) [NOTICE]
/example/example.txt downloaded (5908 bytes, 152196.03KB/sec)
Feb 18 13:16:14 web1 pure-ftpd: (stupid-pure-ftpd @84.56.131.73) [INFO]
Logout.
every
2010 Feb 21
1
Bug#570792: logcheck: The report doesn't support anymore the unicode characters.
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?