Hello, my $TMPDIR (/tmp) is filling up while scanning (large files). I'm running 0.96.3. I run daily scans on files changed within the last 24 hours (which I put into a file and pass to clamd). I configured clamd with the following:
MaxThreads 1 MaxDirectoryRecursion 1 MaxScanSize 4294967296 MaxFileSize 4294967296 my $TMPDIR (/tmp) is only 1G in size and I know clamd does not fill $TMPDIR with a copy of the file and then scan it because I can scan a 4 Gig file and $TMPDIR does not fill up. However, at some point during a scan of large file sizes (not necessarily a large amount of files) $TMPRDIR fills up. So, my question is this, how does clamav use $TMPDIR and how can I safely run scans on files that average 3-4 Gigs in size. I found the following on another post which leads me to believe that clamav copies (or something) the file it's scanning to $TMPDIR prior to scanning but I've tested this and found it to not be the case. "> Could anyone please give me a bit more information about what kind of > damage might be involved, and how to choose safe non-default values for > these settings? > You should have enough space to scan MaxThreads * MaxFileSize * MaxRecursion files, and enough processing power to process MaxScanSize*MaxFiles bytes in a reasonable amount of time, in a worst case scenario." -- View this message in context: http://old.nabble.com/%24TMPDIR-filling-up-maxscansize-maxfilesize-tp29995202p29995202.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
