I believe the developers are hard at work planning for the future this week, so they can probably can give you better answers than I later on.
I suspect some of this may be platform specific, so my answers are based on my macOS experience. clamd scans every file that clamdscan tells it to, so something else needs to keep track of what's new or changed and notify clamdscan to tell clamd to scan them. So that requires tapping into the file system to determine changes in the area of interest. I've never had an issue with using a file while it's being processed by ClamAV, but scans normally take place very rapidly, so I my not have noticed it being locked. Sent from my iPad -Al- > On Mar 15, 2018, at 1:12 AM, Tsutomu Oyamada <oyam...@promark-inc.com> wrote: > > I have two question about the clamdscan; > > 1) Does the clamd skip scanning the files which are scanned before? > I want to know if the clamd remember which files are scanned, and skip them > when the scan is performed again. > > 2) Is there any case that a file is locked by the clamd (user cannot use > that file) during that is scanned? > > T.O _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
