>>If you only have 1G free on /tmp set MaxFileSize to that.
>>MaxFileSize also controls maximum size of file created.
>>>OK, I can do that, but my scans will still fail due to archives in
tmpdir (see below).
> how can I safely run scans on files that average 3-4 Gigs in size?
>> Don't scan files that large, did you ever find a virus in them?
>>> No, I have not found a virus in these large files. But ignoring
them defeats the purpose of scanning for viruses.
>>The input file is not copied, but individual archive members are
>>extracted to tmpdir, scanned, then removed. So you need space the size
>>of the largest archive member.
>>>OK, so it's the archives' that are being extracted to tmpdir. I'll
have to do more testing to find out the general size I'll need: I'm running
on multiple oses and several hunderd servers.
>>If you only scan 1 file at a time, then ignore the MaxThreads.
>>Also the MaxRecursion is a worst case scenario, if you have space for
>>MaxFileSize it should be good enough.
>>>I do scan only 1 file at a time, I'll ignore MaxThreads.
In light of all the above, is there any possibility of ArchiveMaxFileSize,
ArchiveMaxRecursion and ArchiveMaxFiles being added back into the ClamAV
source? I'd like to differentiate regular file sizes/limits from archive
sizes/limits.
--
View this message in context:
http://old.nabble.com/%24TMPDIR-filling-up-maxscansize-maxfilesize-tp29995202p30049612.html
Sent from the clamav-users mailing list archive at Nabble.com.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
