In pursuing the problem of the new worm with a password-protected RAR file, I 
found a problem with ClamAV.

I'm running the SOSDG ClamAV Windows port version 0.90.2-2 (along with runclamd 
and runclamscan).

Declude uses the following string:
C:\clamav-devel\bin\clamdscan.exe --quiet -l report.txt

If I try to use it at a command prompt, I get the lstat() failed error. If I 
type in the full path for my command string, such as 
C:\clamav-devel\bin\clamdscan.exe --quiet -l C:\temp\report.txt 
C:\temp\123456789.eml

it works. The problem is that Declude scans a file in a different directory 
each time, so the path changes. So for Declude to work now, it would require a 
significant change in Declude.

But ClamAV worked before. What changed? Can it be changed back? Is this a 
problem with ClamAV in general, or just with the SOSDG Windows port? Do the 
other ClamAV ports have this problem?

Any suggestions you might have are greatly appreciated.

Gary Steiner









---
This E-mail came from the Declude.Virus mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.Virus".    The archives can be found
at http://www.mail-archive.com.

Reply via email to