[clamav-users] Why clamdscan and clamscan may give different results

[Paul Kosinski]

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 little front-end script to pass
sensible options to clamscan to make it actually useful. (Currently,
clamscan has over 80 options. Are we expected to remember them all when
using the command line?)

P.S. Specifying options via environment variables and/or configuration
files to make command line usage easier is a Unix tradition. And many
GUI programs also allow persistent configuration to ease their usage.


On Thu, 9 Jan 2020 10:06:09 +0100
Matus UHLAR - fantomas <uhlar at fantomas.sk> wrote:

> >On Jan 8, 2020, at 18:25, Paul Kosinski via clamav-users
> ><clamav-users at lists.clamav.net> 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 during the compile stage leading to
> > installation and clamd.conf options only apply to clamd and
> > clamdscan.
> 
> you can pass options to clamscan on command line.
> 
> clamscan is not clamd, therefore it does not pass clamd's config file.
> We can of course ask why there's no common config file for all clamav
> programs (maybe clamav libeary) but that is another issue.