[Logcheck-devel] Bug#391458: logcheck: Please provide a way to configure niceness of log scanning process
Moritz Naumann
bugs.debian.org at moritz-naumann.com
Fri Oct 6 16:15:18 UTC 2006
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 customization to logcheck
could be made which would allow for configuring the niceness of the cron
scheduled log scanning (egrep) processes. I would think other users will
run into the same problem earlier or later, too, as the size of the
logcheck database is unlikely to decrease, but rather to increase over
time.
Thanks for reading,
Moritz
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8)
Versions of packages logcheck depends on:
ii adduser 3.97 Add and remove users and groups
ii cron 3.0pl1-97 management of regular background p
ii debconf [debconf 1.5.5 Debian configuration management sy
ii grep 2.5.1.ds2-5 GNU grep, egrep and fgrep
ii lockfile-progs 0.1.10 Programs for locking and unlocking
ii logtail 1.2.47 Print log file lines that have not
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii nullmailer [mail 1:1.03-3 simple relay-only mail transport a
ii sysklogd [system 1.4.1-18 System Logging Daemon
Versions of packages logcheck recommends:
ii logcheck-database 1.2.47 database of system log rules for t
-- debconf information:
logcheck/changes:
* logcheck/install-note:
More information about the Logcheck-devel
mailing list