If you only want to do one scan per day, you may wish to use clamscan instead of clamd + clamdscan.
If you're doing scans on the commandline, the advantage to using clamd is to reduce load time. You can load once, and then use clamdscan to target multiple files or directories with multiple scan commands. If you're running a single scan once, even if selecting multiple files or directories, then clamscan may be easier: E.g. run: clamscan -r DIRECTORY1 DIRECTORY2 DIRECTORY3 ________________________________ From: clamav-users <clamav-users-boun...@lists.clamav.net> on behalf of neel roy via clamav-users <clamav-users@lists.clamav.net> Sent: Friday, June 7, 2024 10:25 AM To: clamav-users@lists.clamav.net <clamav-users@lists.clamav.net> Cc: neel roy <neelsm...@rediffmail.com> Subject: [clamav-users] Using clamd@ service vs launching clamd from command line Hello, https://docs.clamav.net/manual/Usage/Scanning.html#clamd reads "Once you have set up your configuration to your liking, and understand how you will be sending commands to the daemon, running clamd itself is simple. Simply execute the command: clamd" But after installation I also get "/usr/lib/systemd/system/clamd@.service". Question I have is, if I have only one conf file "/etc/clamd.d/scan.conf" and all I want to do is run scan once a day, what is the advantage of using clamd@ service vs launching "clamd" from command line? And if there is no difference, which approach is recommended and why? Thanks in advance, -Neel.
_______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
