This one time, at band camp, A. Costa said:
> (Uncertainty:  nobody else reported this, so it may be some locally
> corrupt file or local config glitch.)
> 
> Today 'clamscan' doesn't work on my system:
> 
>     % echo hello > /tmp/foo
>     % clamscan /tmp/foo ; echo $?
>     LibClamAV Error: cli_loaddbdir(): Can't open directory 
> /var/lib/clamav//main.inc
>     ERROR: Unable to open file or directory
> 
>     ----------- SCAN SUMMARY -----------
>     Known viruses: 106269
>     Engine version: 0.90.1
>     Scanned directories: 0
>     Scanned files: 0
>     Infected files: 0
>     Data scanned: 0.00 MB
>     Time: 16.322 sec (0 m 16 s)
>     50
> 
> The 'LibClamAV' error message is odd -- "//" doesn't look like it
> belongs in a proper filename.

I don't think that's a problem - it's presumably an artifact of 
pathname concatenation.

> Hope this helps...

It's unreproducible for me, at least:

[EMAIL PROTECTED]:~$ echo hello > /tmp/foo
[EMAIL PROTECTED]:~$ clamscan /tmp/foo ; echo $?
/tmp/foo: OK

----------- SCAN SUMMARY -----------
Known viruses: 304587
Engine version: 0.90.1
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 0.00 MB
Time: 10.142 sec (0 m 10 s)
0

What is the output of 
find /var/lib/clamav -ls
?

Thanks,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        [EMAIL PROTECTED] |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

Attachment: signature.asc
Description: Digital signature

Reply via email to