My experience: vmdk-file can't be properly scanned without accounting for
the vmdk base of the file. They are not files Clamav understands. Just as
zip files need special handling, vmdk files need special handling. VMware
has published the specs. I don't have the time/smarts to process vmdk
On 12/22/06 6:31 AM, "Stephan Brauss" <[EMAIL PROTECTED]> wrote:
> When I scan a 3.5GB file
> (in fact it is a VMWARE vmdk-file and not an archive)
I don't know the format of a VMWare file. Is it useful to scan it (or are
the contents enough unlike what a scanner knows about that problems are
un
On my X86_64 SuSE 10.1 system, equipped with 4GB main memory, I have installed
the "standard" rpm
clamav-0.88.7-1.2.x84_64.rpm that can be downloaded from ftp.suse.com. When I
scan a 3.5GB file
(in fact it is a VMWARE vmdk-file and not an archive) with clamd/clamdscan, all
seems to run ok
unt
Per Jessen wrote:
Jay Lee wrote:
The point of the exercise it to run freshclam *only* when the update
is published, not to run every x hours (or minutes) without knowing if
there is an update.
Looking at my options there...
Why not just run freshclam as a daemon?
Then you really need t
Jay Lee wrote:
> The point of the exercise it to run freshclam *only* when the update
> is published, not to run every x hours (or minutes) without knowing if
> there is an update.
>
> Looking at my options there...
Why not just run freshclam as a daemon?
/Per Jessen, Zürich
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zoran Milic wrote:
> Hi,
>
> Am I the only one with this kind of problem? Is this a bug or my
> missconfiguration?
>
>
> best regards, Zoran
AFAIK, ClamAV and MIME don't go well together yet, so your best bet is
to use an external package for handling
