Arnaud,
I now understand that we do not run the daemon. We update and scan from cron. I stumbled on a work around I *think*
$ sigtool --version
ClamAV 0.99.4/25394/Wed Mar 20 07:52:02 2019
VS
$freshclam -V
ClamAV 0.99.4
Thanks,
Sean Clark <> Sr Network Engineer
“An ounce of prevention is worth a pound of cure”
ServiceNow <> office 425-305-2269
From: Arnaud Jacques <webmaster@securiteinfo.com>
Date: Wednesday, March 20, 2019 at 9:32 AM
To: ClamAV users ML <clamav-users@lists.clamav.net>
Cc: Sean Clark <Sean.Clark@servicenow.com>, Alexandru Cojan <alexandru.cojan@servicenow.com>
Subject: Re: [clamav-users] freshclam -V output
[External Email]
Sean,
Here is the resolution I applied when I get this problem (on Debian OS) :
# clamdscan -V
ClamAV 0.100.0
(not information about loaded databases)
vi /etc/systemd/system/clamav-daemon.socket.d/extend.conf
[Socket]
ListenStream=127.0.0.1:3310
(check if the 2 above lines are present)
systemctl --system daemon-reload
systemctl restart clamav-daemon.socket
systemctl restart clamav-daemon.service
vi /etc/clamav/clamd.conf
TCPSocket 3310
TCPAddr 127.0.0.1
/etc/init.d/clamav-daemon restart
(it worked at this point).
Hope it helps....
Le 20/03/2019 à 13:12, Sean Clark via clamav-users a écrit :