On 07/09/06, Dennis Peterson <[EMAIL PROTECTED]> wrote:
Gerard Seibert wrote:
>
> On a serious note and I do not mean to offend you either; however, if
> you are not going to assist the individual, why ever bother to reply?
Apparently you did not read the thread. I gave him the best advice
possible. Someone gave him a load of crap that suggests clam can't
handle files larger than memory and that it was considered by them to be
a clam bug (conveniently ignoring that files are always capable of being
larger than RAM most people can afford). He swallowed it whole and
started looking for ways to scan only small files.
Yep, I've just tested clamav on a 1700MB file and although it took
17minutes, it didn't crash the server or even use excessive resources.
I thought it sounded a bit strange that it couldn't handle large
files, although I think it might not be a bad idea to exclude them
anyway. Which still leaves me with a crashing server, and nothing in
the logs. Will try running clamscan with the -v and --debug options
and see if it sheds any light.
Casper.
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
