Hi there, On Sat, 9 May 2020, iulian stan via clamav-users wrote:
It's normal that scanning with clamdscan takes a shorter time than clamscan because the virus databases is already loaded (since it's a daemon) and ready for action. For testing purposes(debugging, etc) you can use clamscan for all other purposes use clamdscan where you don't need to wait to load the virus database on each run.
Do be aware that the configurations used by clamscan and clamdscan will in most cases be different, as will the permissions. Refer to the full documentation for configuration details and make sure that you understand the implications of the user and group permissions for the real and effective uids and gids of the scanning processes. -- 73, Ged. _______________________________________________ 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
