logcheck (1.4.5) unstable; urgency=medium A systemd service/timer have been added, which will be preferred over cron. If you have local customizations to the logcheck crontab, such as a different run schedule, you will need to migrate those to the new service and/or timer definitions. (For example, `systemctl edit logcheck.timer`.) -- Mathias Gibbens Sat, 31 May 2025 22:18:22 +0000 logcheck (1.4.2) unstable; urgency=medium Beginning with bookworm, logcheck defaults to checking the systemd journal in addition to any syslog files created by rsyslog or other similar daemons. If you wish to disable either the journal or syslog source, please modify the corresponding configuration file under /etc/logcheck/logcheck.logfiles.d/. -- Mathias Gibbens Wed, 01 Mar 2023 22:14:06 +0000 logcheck (1.2.33) unstable; urgency=low Logcheck's rulefile directory permissions have been changed in this release from 0740 to 4740. -- Todd Troxell Fri, 07 Jan 2005 20:23:00 +0500 logcheck (1.2.19-2) unstable; urgency=low As of version 1.2.19, logcheck no longer runs as root. Logcheck runs as user logcheck which has been created and added to group adm upon configuration. If you have customized your configuration, you will need to be sure that your logs are readable by the logcheck user. -- Todd Troxell Wed, 05 May 2004 12:00:00 +0000 logcheck (1.2.3) unstable; urgency=low Changes to ignore.d directory behaviour Now the ignore.d directories function in an additive manner (i.e. higher levels also include the lower levels): - workstation = workstation + server + paranoid - server = server + paranoid - paranoid = paranoid Also run-parts(8) now controls which rulefiles are included from the .d directories. Please see /usr/share/doc/logcheck for more details. -- Jon Middleton Sun, 12 Jan 2003 23:48:13 +0000