It wouldn't be necessary to make clamscan and clamdscan the same program in this case. One could have clamscan check to see if it was invoked as clamdscan and if so refuse to run. Yes, it should be up to the end user to not screw up his own system, but this one issue has caused enough grief here that such screw ups deserve a bit more direct effect. I think it is entirely reasonable to have clamscan not work if it is called clamdscan.

--
James Lick -- éåæ -- [EMAIL PROTECTED] -- http://jameslick.com/
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users

Reply via email to