Bug#360696: exim4-daemon-heavy: Failed to get write lock forretry.lockfile / exim process hangs with 100% CPU

[Michel Meyers]

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

Andreas Metzler wrote:
 > On 2006-04-04 Michel Meyers <steltek at tcnnet.dyndns.org> wrote:
 >> Package: exim4-daemon-heavy
 >> Version: 4.60-4
 >> Severity: normal
 >
 >> Hello,
 >
 >> I'm having a similar problem as the one mentioned in Bug 314356 :
 >
 >> I communicate a lot with people defined on an SMTP server that uses
 >> greylisting and whenever that server rejects one of my outgoing e-mails
 >> (meaning that exim has to retry on my side), the respective exim process
 >> gets stuck with 100% CPU usage and the only way to get rid of it is to
 >> kill it with signal 9. While the stuck process is there, the mainlog
 >> keeps mentioning messages like these:
 > [...]
 >
 > What does exiwhat say about the stuck process?
 >             cu andreas

Sorry for the late reply, was out of town for a few days.

It states:
31441 tidying up after delivering 1FT0NS-0008AT-0D

Greetings,
        Michel

P.S. Resending, I think I inadvertedly encrypted the mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32) - GPGrelay v0.959

iD8DBQFEOqTh2Vs+MkscAyURAk+uAJ4r1WznxlSikk7nTtqbje5ZjaXokACghPyO
SH7YvqyfQtuY3jBQDsgjhZM=
=I+f2
-----END PGP SIGNATURE-----