Hello Richard, Am Fri, May 16, 2025 at 06:58:44PM +0100 schrieb Richard Lewis: > On Fri, 16 May 2025, 18:40 Helge Kreutzmann, <[email protected]> wrote: > > Am Fri, May 16, 2025 at 06:02:55PM +0100 schrieb Richard Lewis: > > > On Fri, 16 May 2025, 17:29 Helge Kreutzmann, <[email protected]> > > wrote: > > > > > > > Hello Richard, > > > > first of all, to test other configuration, I downgraded logcheck to > > > > the previous version - now everything is back to normal. So this is not > > > > an exim issue or so, but is clearly caused by the updated package. > > > > (Logcheck > > > > is running on this machines for many years). > > > > > > > > > > thanks - all the other lines looked ok, although am confused by the exim > > > output --- my guess is that this is an issue with systemd units exim. i > > > didnt think this would affect the non-hardened unit, but: > > > > > > can you edit the logcheck script, and add a "sleep 30s" to the "end' , > > > after the point the email is sent -- make sure to pick a point that will > > > actually be run, i cant look right now, but search for where > > mime-construct > > > is used. i think this may work -- > > > > I'm not sure I understand what I should do, sorry. > > > > > https://salsa.debian.org/debian/logcheck/-/blob/debian/sid/src/logcheck?ref_type=heads#L328 > > add a new line with a " sleep 30 " before the return (and after the call to > mime-construct (30 seconds is way too long - probably 10s is enough!)
Ok, I added it. So I can report tomorrow what (if) changed.
> >
> > What exact change *in logcheck* could have triggered this?
>
>
> the use of a systemd timer
Looks like a big change so late in the cylce, but then I'm not a
systemd expert.
> Is there
> > anythin *in logcheck* I can (temporarily) disable, like bisecting the
> > difference between the previous version and the current one?
> >
>
> you could also try and confirm it works if systemd is not used
>
> systemctl disable logcheck.timer
> edit the cron.d and remove the code that disables it - logcheck will then
> run from cron
Is this additional to the above change or alternative?
> If not, maybe it is better to return to the previous one, as we are in
> > the hard freeze now[1] …
> >
>
> or, if the fix can be found it can be added to trixie - but we need to
> confirm the issue and fix first.
Well, we are in the hard freeze right now, not at the beginning or the
middle of the Trixi development.
But where possible, I can supply you with information.
Greetings
Helge
--
Dr. Helge Kreutzmann [email protected]
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
