[Logcheck-devel] Bug#623298: logcheck: excessive CPU use by egrep
Arthur Marsh
arthur.marsh at internode.on.net
Tue Apr 19 03:50:14 UTC 2011
Package: logcheck
Version: 1.3.13
Severity: normal
Currently I have an egrep sitting on 64 minutes cpu time that was
run from the logcheck process.
On other logcheck runs, some of the data finally appearing has been
due to fetchnews (part of the leafnode package) and the kernel.
Have any of the developers been looking at which rules use the most
cpu time and how than can be minimised?
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.38.2 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages logcheck depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii cron 3.0pl1-116 process scheduling daemon
ii exim4-daemon-light [mail-tran 4.75-2 lightweight Exim MTA (v4) daemon
ii lockfile-progs 0.1.15 Programs for locking and unlocking
ii logtail 1.3.13 Print log file lines that have not
ii mime-construct 1.11 construct/send MIME messages from
ii sysklogd [system-log-daemon] 1.5-6 System Logging Daemon
Versions of packages logcheck recommends:
ii logcheck-database 1.3.13 database of system log rules for t
Versions of packages logcheck suggests:
ii syslog-summary 1.14-2 summarize the contents of a syslog
-- Configuration Files:
/etc/cron.d/logcheck changed:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
@reboot logcheck if [ -x /usr/sbin/logcheck ]; then ionice -c3 nice -n10 /usr/sbin/logcheck -R; fi
2 * * * * logcheck if [ -x /usr/sbin/logcheck ]; then ionice -c3 nice -n10 /usr/sbin/logcheck; fi
/etc/logcheck/logcheck.conf [Errno 13] Permission denied: u'/etc/logcheck/logcheck.conf'
/etc/logcheck/logcheck.logfiles [Errno 13] Permission denied: u'/etc/logcheck/logcheck.logfiles'
-- debconf-show failed
More information about the Logcheck-devel
mailing list