Is the expected behaviour of clamscan to avoid scanning the root directory as shown below?
$ clamscan -v -r /
Certainly not. Thanks for the report! Clearly a clamscan bug. (Still < 1.0)
$ clamscan -v // ///.bash_history: Access denied. Scanning ///.rnd ///.rnd: OK Scanning ///curl-la.patch
So clamscan wrongly adds another / to the front. (three is okay, two is a network path) Will be fixed ASAP.
My latest huge autotool patch got no response from Thomas so far, so it could need some time to be fixed upstream also.
----------- SCAN SUMMARY ----------- Known viruses: 25864 Scanned directories: 1 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB I/O buffer size: 131072 bytes Time: 0.940 sec (0 m 0 s)
A "clamscan -r /*" does a scan through at least some subdirectories!
-- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
