https://bugs.exim.org/show_bug.cgi?id=728
Andreas Pflug <pgadmin@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |---
Target Milestone|Exim 4.77 |Exim 4.88+
CC| |pgadmin@???
Status|RESOLVED |REOPENED
--- Comment #3 from Andreas Pflug <pgadmin@???> ---
This problem is still present.
On a Debian8 system, I'm tracking deleted files, and sometimes find mainlog.1
files. Logrotate will rename mainlog to mainlog.1, and the next rotation period
the files is zipped and deleted while exim apparently still has it open.
While I haven't seen write access to mainlog.1 after the new mainlog was opened
(i.e. exim works as documented in chapter 51.1), I still find it irritating
that the file is lurking around for days, consuming disk space in a clandestime
way, until I reload exim which will make exim finally close the file.
IMHO exim should close the old logfile as soon as it has detected rotation with
its file stat watcher. I can't see a reasoning why the files should stay open,
let alone for such a prolonged time.
--
You are receiving this mail because:
You are on the CC list for the bug.
