On Tue, 20 May 2025, 17:29 Helge Kreutzmann, <deb...@helgefjell.de> wrote:
> Hello Richard, > Am Tue, May 20, 2025 at 12:41:15AM +0100 schrieb Richard Lewis: > > On Mon, 19 May 2025 at 20:04, Mathias Gibbens <gib...@debian.org> wrote: > > > > > > control: tags -1 + moreinfo unreproducible > > > > > > Having reviewed the messages so far in this bug report, it's clear > > > that something different is happening when logcheck runs under the > > > systemd timer/service, but not cron. However, we don't have a > > > reproducer yet. > > > > i still cannot reproduce the original issue. > > If you need anything else, if I should turn something verbose etc., > please let me know. > im not sure quite what else to suggest. what we need is to know what exim was trying to write. Mybe there is an exim option for that? > All i see is the issue in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106030 so > > hopefully the workaround for that fixes this > > Should I locally implement this, i.e. return to stock logcheck 1.4.4? > cant hurt - you can also do this locally: systemctl edit logcheck # in the editor add: [Service] ExecStart=sleep 180 # im suggestibg a very long sleep, to give more chance to let exim do something - or to write its paniclog
