Re: reaver_cache directory grows without limit.
Nico Kadel-Garcia <[email protected]>
| Newsgroups | gmane.mail.spam.crm114 |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Jan 23, 2009 at 1:55 PM, Paolo <[email protected]> wrote: > On Fri, Jan 23, 2009 at 05:12:30PM +0000, Martin Ward wrote: >> I added an entry to my crontab to fix this: >> >> 45 * * * * find $HOME/.crm114/reaver_cache -type f -mmin +60 | >> xargs rm -f >> >> This checks the cache every hour and deletes anything more than an hour old. > > indeed, that's what users are - more or less implicitly - supposed to do ;) > It's been said on ML, but perhaps not (clearly) documented (yet) in the src. > > Note that your crontab line would be much more efficient using find(1)'s > -delete internal command, if your version supports it, or rm(1) via its > -exec directive, ie > > $ find $HOME/.crm114/reaver_cache -type f -mmin +60 -delete >/dev/null 2>&1 > $ find $HOME/.crm114/reaver_cache -type f -mmin +60 -exec rm -f "{}" \; >/dev/null 2>&1 > > BTW, BlameSegfault is not much 'latest stable'. Paolo, doing '-exec rm -f ' is not as efficient in my experience as you might think. For operations involving lots of files, it involves starting up one heck of a lot of unnecessary shells. And with the oddities some people wind up doing in their .bashrc's or other shell configuration tools, it can become even more burdensome. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword