Author: Jasen Betts Date: To: exim-users Subject: Re: [exim] [clamav-users] problem reading socket while updating
database
On 2015-07-08, Ian Eiloart <iane@???> wrote: >
>> 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.
for multiple addresses how about 127.0.0.1 and 127.0.0.2 :)
but first multiple sockets are worth trying. there's a chance
that the documentation is wrong.
>
> --
> Ian Eiloart
> Postmaster, University of Sussex
> +44 (0) 1273 87-3148
>
