-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ray Liere on 2/2/2008 7:47 AM:
| I was thrown by it because I had written some code that "assumed"
| that, regardless of what timestamp precision existed on a particular
| computer, all of linux would be consistent and either use the extended
| precision or not.
| utimes("jnkcopy2", {1201833653, 245502}) = 0
No - the problem is more fundamental than that: that older versions of
Linux do not even HAVE a way to set timestamps less than microsecond
resolution. Your trace shows that coreutils used utimes, which used to be
the only way to set timetamps, but which inherently does not support
nanosecond resolutions. futimensat is a relatively new invention, and
prior to it, there just wasn't a way to set the necessary precision. But
you are also right that older coreutils won't use futimensat even if it is
available on a newer kernel; you need new software on both fronts to get
the advantage of setting nanosecond resoultion on timestamps. Once you
have the new syscall, and the new coreutils that uses the new syscall,
then resolution is set to the maximum allowed by the filesystem that the
file is on (not necessarily the same granularity on different file systems).
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHpIfv84KuGfSFAYARAp4DAJ4gPnQ+UJJ06W+hXR1IEPtmmxT+ogCeIYys
CGmRdvx0J+A/3tLM9C1oYAo=
=Afu9
-----END PGP SIGNATURE-----
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
