On Jan 8, 2020, at 18:25, Paul Kosinski via clamav-users
<[email protected]> 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.
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"One World. One Web. One Program." - Microsoft promotional advertisement
"Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler
_______________________________________________
clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
