clamdscan uses the clamd daemon to perform scans, and since it runs as user 
clamav (or the like), it does not have enough permissions to scan calling 
user's directories if they are protected.  

For instance, my .tvtime subdirectory in my home will be scanned by clamscan, 
but will generate errors using clamdscan.  I understand why, but isn't this 
some sort of shortcoming of this design?

I will use clamscan, not clamdscan, until this can be addressed.

BTW, I am upgraded to 0.81; same Mandrake 10.1 platform.

Thanks,
Hal
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users

Reply via email to