Bug#476958: exim4 logrotate do not restart exim

[Klaus Ethgen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Marc,

Am Fr den  2. Mai 2008 um 11:34 schrieb Marc Haber:
> I would like to know what are the last lines of mainlog.2.gz, whether
> they were written after mainlog was rotated to mainlog.1,

2008-05-01 06:26:27 1JrQND-0002vo-GV Completed
2008-05-01 06:26:28 1JrQM9-0002rp-7a <= xxxx at xxxxxxxxx U=xxxx P=local S=69040
2008-05-01 06:26:29 1JrQM9-0002rp-7a => xxxxx <xxxxxxxxxxxxx at xxxxxxxxx> R=procmail T=procmail_pipe
2008-05-01 06:26:29 1JrQM9-0002rp-7a Completed
2008-05-01 06:26:37 1JrQNR-00038O-9O <= xxxx at xxxxxxxxx U=xxxx P=local S=9322
2008-05-01 06:26:37 1JrQNR-00038O-9O => xxxxx <xxxxxxxxxx at xxxxxxxxx> R=procmail T=procmail_pipe
2008-05-01 06:26:37 1JrQNR-00038O-9O Completed

Well, not really secret but I X-out the privacy stuff.

> and what exiwhat says about process 4349.

I cannot as I just did restart it manually. I have to wait for the next
one.

> I do, however, think that this is a behavior local to your system,
> since the results are rather blatant, and we have been shipping exim
> 4.63 with this log rotation scheme as part of our stable default
> install for more than a year and the issue would have been surfacing
> before.

Maybe other just ignored it, didn't get rid of it or implemented the
suggested fix themself. I don't know.

What I know is that I use exim for long time now and had the fix done on
my mail server before but missed to move the logrotate file to my new
mail server. So the bug was hitting me again so I decide to report the
bug finally. I do not know when I did the change in the logrotate file
on the other mail server. It was long ago. So this Bug is in exim for
long time now.

> I am therefore not prepared to implement the change you suggested.

Do it as you wish. It is simple to implement; also for the local
administrator. Unlikely it is hard to see if you have no tool checking
regularly for open deleted files.

Again I switch off the work around to have the failed behaviour next
time again. Is there anything else I should find out when it happens
again?

Gruß
   Klaus
- -- 
Klaus Ethgen                            http://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus at Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSBrulZ+OKpjRpO3lAQI4zgf7B7SvM32OAD18VZkWJJAFHZOrIPzDxd0k
tDIr56pfOpf8AjtUzhiEVKn8urKLFgIWyCH0iRBvd3/XbU4vXmKUcv5U73+zSlGF
iCm6yAy04RRNvWlTyHb2tem63vm3HnAVEP79+dk/3d+qbDtafGidsNNagc+QnAI8
ka31PlWrornSVA0H68gk4FkB9u7qdHW/lg2FiZclDo7qWQBaayCPI7FAy+pKa0RU
F0LnUZaCP2n/tfqel6zdLeTZtMayjs3khnvSOz1FjKHp02cYeRH7T7W2y9O8AQU3
HuJCqcLIxofYRAMbjgs+jLhsadU2wFMnrjGOXqFt/T2J0au+Nqg2Dg==
=6PRD
-----END PGP SIGNATURE-----