On Tue, Dec 12, 2006 at 01:32:27PM -0500, Mark Hennessy said: > I've seen some instances where clamd will sometimes leave large directories > named like clamav-[hash] or large files named like clamav-[hash] and not > clean them up after they're done with. As far as I can tell, clamav was not > stopped/restarted during the timeframe where these were being worked on. The > thing that seems to be common for them is that they are e-mails that > contained very well compressed attachments, like gzipped text attachments for > example, that when extracted are in excess of 100MB each. > > Why might this happen? What would be suggested in making sure that clamav > doesn't leave this sort of thing around long-term? I've been told by my boss > that it's not an option to leave any e-mail unscanned, regardless of size. > > I'm using FreeBSD 4.11 and 6.1 and the latest ClamAV, postfix as my MTA, and > amavis-new as my milter.
The short term option would be to use something like tmpreaper to keep /tmp under control until the real problem is sorted out. I'm afraid I've never seen this problem before, and the permissions all look fine in the other messages I've seen. -- -------------------------------------------------------------------------- | Stephen Gran | Oh, well, I guess this is just going to | | [EMAIL PROTECTED] | be one of those lifetimes. | | http://www.lobefin.net/~steve | | --------------------------------------------------------------------------
signature.asc
Description: Digital signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
