Christoph Cordes wrote: > Am 10.08.2007 um 23:16 schrieb Marshall Dudley: > > >> I was running clamscan, and the var partition of the drive filled up. >> This partition had 300 Meg free on it, and clamscan created a huge >> number of files like mixedtextportion05GJ4k in the >> /tmp/clamav-ec6d3e4e4e253eaf directory and filled it up. To make >> > > Could it be that you scanned some large .mbox file? > No, they are all on the /var partition, which I did not scan, since last time it reported hundreds of Windows worms in mailboxes, when this is a Unix system. >> matters worse, I had a difficult time deleting them to get the system >> back up because when I tried to do a "rm *" it reported that the file >> list was too long, so I had to delete them a few at a time. >> > > Why not "rm -rf /tmp/clamav-ec6d3e4e4e253eaf" ? > > >> How can I prevent clamscan from doing this? >> > > If you scan a file in mbox format - with, let's say 500 mails, Clam > extracts every mail out of it and also every attachment and - if the > attachment is a zipfile, or rarfile or some other container, the > files are extracted as well and creates a file for it. This way it's > easy to create tons of files that of course use a lot of space. So > you could provide more temp space, tell clamscan to use an alternate > directory for the temp files - on a disk with more space - or avoid > to scan mbox files. If it was an mbox file that caused the problem. > > > OK, I will hit the documentation, to see how to do that. It was putting it in a temp folder of the /var partition, which is under a gig, I can use the /usr partition, which has 20 or so gig free on it. I really have no idea what it was scanning since the screen filled up with drive full messages.
Marshall _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
