> My experience: vmdk-file can't be properly scanned without accounting for > the vmdk base of the file. They are not files Clamav understands. Just as > zip files need special handling, vmdk files need special handling. VMware
> has published the specs. I don't have the time/smarts to process vmdk > files, sorry. You don't have to. I do not want to scan vmdk-files, but I "accidentially" had two images in my home directory, and I wanted to scan /home. I know that clamav does not understand vmware images, and therefore an image should be just a data file like many others in my home directory and handle it like that. Therefore, I do not think that the problem is vmware related, I guess that any file of this size maybe causes it. I will try out after chistmas with a mutli-GB file containing garbage. Btw. I tried to find an option to exclude files with given extension, or files that are larger than a given size, but without success. Are such options available? _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
