David Fix wrote:
The for construct doesn't have this issue. :)
Good to know.
Bruce, since you brought this up, can you run a test to see if the "for"
method is faster than using find?
The way we use it, a recursive find in /tmp or a "rm -r /tmp/*" in a
for-loop has the exact same result. Using find would allow easier
changes down the road if we ever need to have more fine-grained control
which files and/or directories are removed or left alone.
If there is a large performance difference in find vs. for, then I'd
like to consider using "for" until such a need actually arises to use
the more versatile "find" method.
--
Gerard Beekmans
/* If Linux doesn't have the solution, you have the wrong problem */
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
