On Sat, May 17, 2025 at 04:14:34PM +0000, Helge Kreutzmann wrote:
Am Sat, May 17, 2025 at 05:44:03PM +0200 schrieb Marc Haber:
On Sat, May 17, 2025 at 01:44:57PM +0000, Helge Kreutzmann wrote:
> In /etc/exim4 three files mention procmail:
>
> exim4-config: /etc/exim4/conf.d/transport/30_exim4-config_procmail_pipe
> exim4-config: /etc/exim4/conf.d/router/700_exim4-config_procmail
> exim4-config: /etc/exim4/exim4.conf.template
>
> But I never edited them directly, only via Debconf (probably when I
> installed the machine.
If you don't use procmail, you should deinstall it. Exim can deliver by
itself.
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?
I don't think so. I just suggest disabling it to make things a bit
easier to reproduce for Richard. It's like building a minimal
reproducer, and taking software that should not interfere her out of the
equation makes things easier if it is not necessary.
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.
That is boilerplate code to make the cron job do nothing on a system
that has systemd as pid 1.
file /run/systemd/system:
/run/systemd/system: directory
That is the common way to identify whether your system has systemd as
pid 1. It is a very common idiom, see codesearch.debian.net.
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
