On Tue, Dec 12, 2006 at 05:57:01PM -0800, Joe Pace said: > Stephen Gran wrote: > >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. > > > Thank you -- this answers my question really, which was going to be > whether these files can safely be removed while clam is running.
Once clam has spit out the error that it couldn't remove the directory, it's finished with the contents and it's safe to remove them. tmpreaper looks for files and directories older than a configurable limit, so it is perfect for what you want to do. I think there are even include and exclude directives, so you could run it twice a day look for files named clamav-XXXX that are older than 6 hours or so, and probably be perfectly safe. > I'm wondering whether it could be that the directory removal is failing > because it's not empty, i.e., there might be a problem with the removal > of the contents prior to the directly being unlinked. Yes, that is my guess, not that I see /tmp has reasonable permissions and the directories aren't empty. I have no idea why clamav has not unlinked all the files underneath it, though. Does AIX have the equivalent of linux's /proc/$pid/fd/ ? It would be nice to know if those files are open or not. Take care, -- -------------------------------------------------------------------------- | Stephen Gran | Have you seen the latest Japanese | | [EMAIL PROTECTED] | camera? Apparently it is so fast it | | http://www.lobefin.net/~steve | can photograph an American with his | | | mouth shut! | --------------------------------------------------------------------------
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
