root@ip-10-64-205-19 bin]# clamconf -n
Checking configuration files in /etc
Config file: clamd.d/scan.conf
--
LogFile = "/var/log/clamd.scan"
LogFileMaxSize = "10485760"
LogTime = "yes"
LogSyslog = "yes"
LogVerbose = "yes"
LogRotate = "yes"
ExtendedDetectionInfo =
Hi there,
On Tue, 29 Jun 2021, Lopez, Carmelo via clamav-users wrote:
I am trying to start clamonacc on a rhel 7.9 machine, but I am
getting an error. Clamd daemon is running. Please see error below:
root@ip-10-64-205-19 bin]# clamonacc
ERROR: ClamClient: Could not connect to clamd, Couldn't
I am trying to start clamonacc on a rhel 7.9 machine, but I am getting an
error. Clamd daemon is running. Please see error below:
root@ip-10-64-205-19 bin]# clamonacc
ERROR: ClamClient: Could not connect to clamd, Couldn't connect to server
ERROR: Clamonacc: daemon is local, but a connection
We will have lots of clamav clients so that’s why I built a private mirror.
I’ve resolved the issue. Apparently selinux was preventing the clamd daemon
from starting. After disabling it, clamd started fine.
From: clamav-users on behalf of G.W.
Haywood via clamav-users
Date: Friday, June 25,
Hello.
I submitted it over a week ago, and got a response saying that "Our
initial assessment has verified the sample as a threat & we will be
publishing signatures for ClamAV," but neither the ClamAV scanner in
Jotti nor the one in Virus Total detects it.
You can verify for yourself; the
Hi there,
On Sun, 27 Jun 2021, Paul Rogers via clamav-users wrote:
So I rebuilt curl-7.50.1 ...
https://curl.se/docs/vuln-7.50.1.html
--
73,
Ged.
___
clamav-users mailing list
clamav-users@lists.clamav.net
