This may be unique to clamscan on linux on z/series.
I cannot provide the access, as this is all internal system stuff, but I'm
willing to grab any files that might shed light on things. Essentially be
the gopher.
On Thu, 20 Jan 2005 10:05:58 -0600
[EMAIL PROTECTED] wrote:
> 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Í!
On Thu, 20 Jan 2005 at 10:05:58 -0600, [EMAIL PROTECTED] wrote:
> [...]
> 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 ope
On Thu, 2005-01-20 at 16:05, [EMAIL PROTECTED] wrote:
> LibClamAV Error: cl_loaddb(): Can't open file ¸WÍ!´>Í!2íL/daily.cvd
> ERROR: Unable to open file or directory
>
How specifically did you run configure, did you supply a --with-dbdir
option?
-trog
signature.asc
Description: This is a dig
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
