In this regard, Abigail's original suggestion seems best -- using a pipeline file handle that runs "find" is very fast and economical in terms of memory, and only keeping track of the 10 largest files seen so far will assure that the script won't blow up as the file space gets bigger.
In reply to Re: finding top 10 largest files
by graff
in thread finding top 10 largest files
by bfdi533
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |