Yes of course you can pass options to clamscan on the command line
(it's what I did in my 4th example). But my point is that it makes
clamscan much harder to use in practice, as with only the default
values for the options, clamscan can be very misleading.
For now, I guess I'll have to write a lit
On Jan 8, 2020, at 18:25, Paul Kosinski via clamav-users
wrote:
It seems to be because clamscan does not respect the options in clamd.conf...
On 08.01.20 18:38, Al Varnell via clamav-users wrote:
That's correct and AFAIK, has always been the case. clamscan
configurations is accomplished dur
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
