Hi Micah,
I'm sorry for mistake, the file I sent you is OK apart the commented
line. Probably the mistake was during the copy from VM to host (a file
exchange) .
I've controlled the config file and is all ok, in any case I've done
another test.
1. stop the clamd
2. verify the configuratio
Hi Domenico,
Try changing:
#LogClean yes
to:
LogClean yes
(delete the #)
Micah Snyder
Software Engineer
Talos
Cisco Systems, Inc.
On Jan 14, 2018, at 1:29 PM, domenico
mailto:mado...@gmail.com>> wrote:
#LogClean yes
___
clamav-users mailing lis
Hi Micah,
thanks for your reply. This is my configuration file
/etc/clam.d/scan.conf (if I do "ps -ef |grep clam", I have
"/usr/sbin/clamd -c /etc/clam.d/scan.conf --foreground=yes):
Domenico
Hi Domenico,
Can you share your clamd.conf file?
I did a quick test with clamd, clamdscan and verified the behavior. If you
scan a directory, you should see “OK” or “FOUND” for each file that is scanned
in your log file (typically /tmp/clamd.log).
Micah Snyder
Software Engineer
Talos
Cisco Sy
Hi there,
my name is Domenico and I'm new in this list. I know Clamav for many
years but as simple user.
Now I need to deploy a particular application that divides infected
files from clean files. Shortly I have a directory to scan using the On
access function, if the incoming file is infected
Hi,
I’ve just switched from using sockets to using TCP, so that I can make
Exim/ClamAV more resilient. The idea is that when Exim has access denied
because clamd is re-reading the database, it can select another clam server.
When testing the new service, I noticed that "LogClean yes" doesn’t se
