Is it possible to run clamonacc on the file server (e.g., Samba)?
Or are there too many local accesses to those files.


On Wed, 22 Jan 2020 17:32:45 +0000
Paul Hasenohr via clamav-users <clamav-users@lists.clamav.net> wrote:

> Dear List,
> 
> 
> Would anyone have some suggestions/inputs to provide?
> 
> 
> Thank you in advance,
> 
> Paul
> 
> 
> ________________________________
> From: clamav-users <clamav-users-boun...@lists.clamav.net> on behalf
> of Paul Hasenohr via clamav-users <clamav-users@lists.clamav.net>
> Sent: Monday 13 January 2020 14:23 To: clamav-users@lists.clamav.net
> Cc: HASENOHR Paul (JRC-ISPRA-EXT)
> Subject: [clamav-users] Clamonacc listing all content of watched dirs
> on startup
> 
> Hello,
> 
> I am currently testing clamav 0.102.1 on Linux (within a Debian
> Buster docker container) to execute on-access scans on folders
> located on an external network storage mounted via a fuse client. The
> issue I am facing is that, when clamonacc starts, it is listing
> every single file and directory under the directories specified in
> the file passed as argument to the --watch-list parameter. The
> folders to be watched containing a few thousands files/folders,
> launching clamonacc overloads the file server with stat requests and
> I have to stop clamonacc before it is ready in order not to bring the
> file server down. There is no problem in watching small folders (with
> tens of files) located on this file server though. Also watching
> folders of any (?) size part of the local file system works fine.
> 
> Is the behaviour I am experiencing to be expected? Is there a way to
> use clamonacc with network based filesystems? Thank you in advance
> for your answers and suggestions.
> 
> Best regards,
> Paul Hasenohr

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
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

Reply via email to