Re: [exim] [clamav-users] problem reading socket while updat…

Top Page
Delete this message
Reply to this message
Author: Ian Eiloart
Date:  
To: Jon Gerdes
CC: exim-users@exim.org
Subject: Re: [exim] [clamav-users] problem reading socket while updating database

> On 8 Jul 2015, at 09:45, Jon Gerdes <gerdesj@???> wrote:
>
> On Wed, 2015-07-08 at 08:34 +0000, Ian Eiloart wrote:
>> Apologies for cross posting. This question is about Exim and clamd. Specifically, how can we deal with a clam daemon that’s unresponsive (for five minutes) while updating rules. The obvious thing would be to wait a bit longer rather than time out, but I can’t see a control for that. I have some alternative suggestions, of which (3) below seems most promising, if somewhat complicated.
>>
>>
>
> Straight off the top of my head without any research:
>
> Sounds like you need a cluster of ClamAV or multiple daemons that are
> updated at different times. Exim *may* be able to handle multiple
> daemons/sockets or you need a load balancer like HA Proxy to act as a
> front end.
>
> Cheers
> Jon


Yes, that was my "(3) below". The docs say you can list multiple IP addresses, but not multiple UNIX sockets for this purpose. But I think the question related to a setup with a single host with limited resource. If funds are available for new machines, commodity modern hardware could probably cope and none of the complexity would be required.

--
Ian Eiloart
Postmaster, University of Sussex
+44 (0) 1273 87-3148