>... I noticed that the estimates are basically tar operations with
>all of the ouput going to /dev/null. That is what's taking the time.
>Not to get the file's size, but to move the date through that system
>pipe into /dev/null.
Nope. Tar knows it is writing to /dev/null and optimizes out the open(),
read() and write() calls so there is no data motion.
I think the time is being spent traversing the directory tree and
stat()ing the things it runs across. In other words, it's doing pretty
much what your find would do.
Sigh.
>--jason
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
