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:12 AM, Christoph Pleger <[email protected]>
wrote:
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 that, close to the
time of the ISP change, I must have made an update of the clamav package
that changed user and group ownership of the local socket without my
knowledge.
But TCPAddr was and is not enabled; clamconf says:
TCPSocket
disabled
TCPAddr disabled
Regards
Christoph
_______________________________________________
clamav-users mailing list
[email protected]
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
clamav-users mailing list
[email protected]
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
clamav-users mailing list
[email protected]
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
