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

tags 391458 wontfix
thanks

Please check /etc/cron.d/logcheck -- logcheck is already running
with nice value 10. If this gets in the way with regularly working
on the system, your problems are likely elsewhere.

control: tags -1 - wontfix
control: tags -1 + confirmed
control: block -1 by 1020328
thanks

This bug - asking for configurable nice level - can be closed once we
introduce a sustemd unit - the nice level of the unit can be easily
customised via an override file.

(and non systemd users can edit the cron script per message below from
2006! )

so propose to close this one once 1020328 is fixed ie post bookworm (unless
any objections)

...