https://bugs.exim.org/show_bug.cgi?id=728
--- Comment #8 from Jeremy Harris <jgh146exb@???> ---
Hypothesis: logwrites are being done infrequently by this process, only for
exceptional conditions (as you don't log new connections), one such does not
close the log after, and this is only detected on the next logwrite attempt.
I'm not seeing it in production as I do log new connections, so it happens but
only briefly. Would adding "pid" to your log_selector be feasible, with your
log volume? We might then nail down the messages coming from the daemon
process.
I guess the issue will be any post-processing you do on logs.
--
You are receiving this mail because:
You are on the CC list for the bug.
