Re: reaver_cache directory grows without limit.

Paolo <[email protected]>
Newsgroups gmane.mail.spam.crm114
Message-ID <20090123185535.GA31734@localhost>
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

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.