I've been weighing the differences of clamscan vs clamdscan via clamd... and I have encountered something that is eluding me as to what the cause was....
When I invoke clamscan, I get an error that it cannot find the daily.cvd file. That points to a configuration problem, but the path it tried to look on appears to be corrupted. LibClamAV Error: cl_loaddb(): Can't open file ¸WÍ!´>Í!2íL/daily.cvd ERROR: Unable to open file or directory When I point clamscan at the /var/lib/clamav/daily.cvd with the -d option, all is well. When I run clamdscan and use the clamd process to do the work, I get no errors like thie either. I am trying to make a determination as to which method is more efficient. Clamscan or clamdscan, so undertanding this error is of paramount importance in making that comparison. I am running this on Suse SLES8, with service pack 3 installed, on IBM z/Series (mainframe) hardware. Clam was built from the version .80 sources on a 'clean' system, (meaning no previous clam AV) I also tried .80rc1 to see if that would resolve the issue but it didn't. The text '¸WÍ!´>Í!2íL' on the path in the above error looks a LOT like what you get when you have an EBCDIC--->ASCII translation issue, which shouldn't come into play here being that linux on the mainframe used ASCII coding, and not ebcdic. I just toss that out there because it is an observation. It may/may not have bearing. If this is a configuration issue, I cannot seem to locate where it would be set in either of the configuration files I know about (clamd.conf and freshclam.conf) If anyone has some enlightnenment to share with this marble-hard head of mine, I would greately appreciate it. - James Melin _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
