Paul E Condon wrote:
> However, it does NOT set the mtime the full precision when
> files are extracted from the .tar file. It only restores
> the integral part of the second. The fractional part is all
> zeros.
Perhaps if both cp and tar are doing the same thing then the problem
is outside the co
Paul E Condon <[EMAIL PROTECTED]> writes:
> The mtime of a file is not copied fully when -a option is
> invoked. This can be seen only when --full-time is used to display the
> original and the copied files. In particular the last three digits of
> the copy mtime (the nano-seconds part) are always
I just did some similar tests of tar:
tar appears to store a correct, full precision mtime in a .tar
file, and use that full precision mtime when deciding whether
to write a new copy of a file when processing -u option.
However, it does NOT set the mtime the full precision when
files are extracte
The mtime of a file is not copied fully when -a option is
invoked. This can be seen only when --full-time is used to display the
original and the copied files. In particular the last three digits of
the copy mtime (the nano-seconds part) are always zero in the copy.
This plays nasty when one attem
