That's correct and AFAIK, has always been the case. clamscan configurations is
accomplished during the compile stage leading to installation and clamd.conf
options only apply to clamd and clamdscan.
-Al-
On Jan 8, 2020, at 18:25, Paul Kosinski via clamav-users
wrote:
>
> It seems to be becau
Having built ClamAV 0.102.1 a few days ago, I stumbled on the following
unfortunate behavior (which is probably not related to 0.102.1), and
have a suggestion to remedy it.
I recently did a backup from a Win 7 Pro machine to a directory on our
CIFS server and decided to try running ClamAV on the l
System is Ubuntu 18.04.3, just upgraded to 0.102.1+dfsg-
0ubuntu0.18.04.2 this morning. Since the upgrade whenever freshclamcron
runs besides the usual output in my syslog the cron daemon mails me
this - https://pastebin.com/ef0Zv6d0 The command line for freshclamcron
is
/usr/bin/freshclam --confi
