On Sat, May 17, 2025 at 04:14:34PM +0000, Helge Kreutzmann wrote:
I use procmail on several machines, but right, on this one it is not
(much) used. I just wonder - is procmail incompatible with the updated
logcheck?

No, it's just to make exim's processing easier.

Before the update I get mails with the subject:
Reboot: twentytwo.helgefjell.de 2025-05-16 15:54 +0200 System Events

After the reboot, now mails with this subject are sent; however, the
content is there (i.e. the filtered logs from the reboot are sent).

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)

I guess one of the messages come from the old cron job which might not be disabled properly, and the other one from the new systemd timer.

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Reply via email to