Thanks for closing the event here. It doesn't happen enough.
dp
On 12/14/16 2:54 PM, Steven Morgan wrote:
Thanks, there was a little coding error. Following the connect() failure on
the local socket, the code was not checking if the TCPAddr option is
enabled.
Steve
On Wed, Dec 14, 2016 at 3:1
Thanks, there was a little coding error. Following the connect() failure on
the local socket, the code was not checking if the TCPAddr option is
enabled.
Steve
On Wed, Dec 14, 2016 at 3:12 AM, Christoph Pleger
wrote:
> Hello Steve,
>
> > Looking at the code, it appears that the error message oc
Hello Steve,
> Looking at the code, it appears that the error message occurs when the
> clamd/clamdscan parameter "LocalSocket" is disabled, or it is enabled and
> the socket connect() call fails, and also the TCPAddr parameter is
> specified.
Thank you for that hint. It brought me to the finding
Hello Christoph,
Looking at the code, it appears that the error message occurs when the
clamd/clamdscan parameter "LocalSocket" is disabled, or it is enabled and
the socket connect() call fails, and also the TCPAddr parameter is
specified.
Can you inspect and/or send the output of the 'clamconf'
Hello,
some weeks ago, I changed my ISP and with that, for the first time got a public
IPv6-address for the computer where clamd/clamdscan are running on. Now, I
realized that from the moment when the provider switch took place, all virus
checks failed with the following error message in the ma
