[email protected] wrote: > Thanks for the suggestion Platonides. After some digging around it appears > that I have the same problem identified at > http://readlist.com/lists/lists.clamav.net/clamav-users/1/6452.html which > looks to be a problem with clamdscan passing a path within the chroot to > clamd which typically won't exist. To test this one can 'touch > /var/www/tmp/test' then 'chroot -u www /var/www /usr/local/bin/clamdscan > /tmp/test' and it will fail with '/tmp/test: lstat() failed: No such file or > directory. ERROR'. Now if one executes 'touch /tmp/test' and tries to scan > within the chroot again it will work (barring any permissions problems). > What I need is a way to tell clamd to append the chroot path onto the path > supplied by clamdscan or trick clamdscan to not check for file existence > since clamdscan check > s if the path is valid inside the chroot then passes the path directly to > clamd.
Try passing --fdpass or --stream to clamdscan. _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
