On 19-Nov-2002 at 12:41:03 Ralf G. R. Bergs wrote:
> I'm still seeing Exim processes that run for half an hour or even longer.
[snipped]
> The only thing I can think of what could be going wrong is that the calls
> to SpamAssassin during SMTP time take that long. I've already removed the
> Razor calls from SpamAssassin because I suspected them and I don't see
> great benefit from Razor (V1), but this didn't help. My DNS system is
> "sane," i.e. DNS calls don't take more than a fraction of a second.
>
Yes, I used to see this. Haven't for some time now.
> Is there any option (I don't think so) that would allow me to set a
> maximum lifetime for Exim son processes? And if processes haven't died
> after that time Exim would automatically kill them? Do you think that
> such an option would be useful in case it's not already there?
>
Are you using the 'sa-exim' that is available? I wrote our own smaller
version, but left out the bit that setup a timer (this, hopefully, catches
any runaway processes). We then had the problem you describe. So I put some
timer code in, SA runs for about 4.5 mins and then gets aborted, and since
then we've had no runaway processes. Could just be luck of course! :-)
One thought. sa-exim sets up the timer to kick the spamc/spamd process. If
you are using options to specify who spamc/spamd runs as then maybe sa-exim
doesn't have premission to abort the process.
I've thought the problem has definitely been in SA, but is probably
dependant on what is being sent to it. We are still using 2.40 and so it may
'hangup' when receiving something weird, the newer versions may be better.
Regards,
John.
------------------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: jhorne@???
PGP key available from public key servers
