Steven Stern wrote:
On Sat, 19 Jun 2004 10:09:48 -0600, Dan Egli <[EMAIL PROTECTED]>
wrote:
I've encountered this bug a few times:
[EMAIL PROTECTED] test]# touch file1 [EMAIL PROTECTED] test]# touch file2 [EMAIL PROTECTED] test]# touch file3 [EMAIL PROTECTED] test]# ls file1 file2 file3 [EMAIL PROTECTED] test]# clamdscan file1 file2 file3 ERROR: Can't access file file1 file2 file3 file1 file2 file3: No such file or directory
The same thing happens in 0.73. Reading the man page, it seems that it is a
WAD.
clamdscan [options] [file/directory]
clamdscan scans one file or one directory tree
clamscan works on multiple files.
--
Steve
but I cannot scan a DIR either.
[EMAIL PROTECTED] root]# clamdscan $PWD /root: Can't access the file ERROR
----------- SCAN SUMMARY ----------- Infected files: 0 Time: 0.001 sec (0 m 0 s)
Can someone kindly explain why on earth you would write a scanner that only scans ONE FILE? The whole point of clamdscan is it's supposed to be faster than clamscan because it let's the daemon do the scanning, and it just acts as an interface. Doesn't make much sense to then cripple it by only working on one file at a time.
Just a guess but I'd bet it doesn't scan directories and files the run-as user has no access to.
dp
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
