On 2007-03-06 09:03:46 +0100, Jim Meyering wrote: > Would you please try changing this definition > (from src/remove.c) to e.g., 200 or 2000, > > CONSECUTIVE_READDIR_UNLINK_THRESHOLD = 10 > > and see if it lets you use "rm -r ..." with no errors?
I've tried 2000, and no longer get the problem with this value. > If this turns out to be a general problem, there's always > the possibility of rewriting rm to use a different strategy: > read all entries into malloc'd storage the first time, rather > than reopening after processing each sub-directory. This solution could be a problem with large directories, like mailbox archives stored under the maildir format. Though machines that need to read such directories probably have enough memory, I think the memory used should be bounded. Also, if when doing a "rm -r", some files are removed by another mean at the same time, this shouldn't prevent rm from removing everything. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
