Hello Richard, Am Sat, May 17, 2025 at 06:58:56PM +0100 schrieb Richard Lewis: > On Sat, 17 May 2025 at 17:14, Helge Kreutzmann <deb...@helgefjell.de> wrote: > > The cron.log says (before the update): > > 2025-04-14T00:02:01.739639+02:00 twentytwo CRON[11492]: (logcheck) CMD ( > > if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi) > > > > and after the update: > > 2025-05-17T18:02:01.470178+02:00 twentytwo CRON[110761]: (logcheck) CMD ( > > if [ ! -d /run/systemd/system ] && [ -x /usr/sbin/logcheck ]; then nice > > -n10 /usr/sbin/logcheck; fi) > > > > So the cron commands changed during the update. > > yes - the cron job is still running, but only if you are not booted > under systemd > > > > Should I revert this and look how it behaves? > > you could try - i predict you will get then get 3 emails: one from > cron, and the same 2 from the timer
I tried this now, and it is the opposite:
root@twentytwo:~# cat /etc/cron.d/logcheck
# /etc/cron.d/logcheck: crontab entries for the logcheck package
# These do nothing under systemd because the systemd timer will take precedence
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
@reboot logcheck if [ ! -d /run/systemd/system ] && [ -x
/usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck -R; fi
#2 * * * * logcheck if [ ! -d /run/systemd/system ] && [ -x
/usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi
2 * * * * logcheck if [ -x /usr/sbin/logcheck ]; then nice -n10
/usr/sbin/logcheck; fi
And now I get *one* e-mail again. The first had the exim error still,
but the second did not.
I'll report in ~ 30 minutes, if the error message has indeed vanished.
Greetings
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
