Paul Smith <psmith <at> gnu.org> writes: > Your attempt to reproduce the behavior is invalidated by the fact that > you didn't duplicate the real conditions: in your test you copied one > file to another in the same directory. In the real environment you > copied one file to a completely different filesystem, and not only that > but it was a different TYPE of filesystem (local, presumably ext3 or ufs > or something, vs. NFS).
Here's an example using gzip where the time gets truncated. This is a very close reproduction of one of my actual problems --- I verified with strace that gzip is using only the NFS filesystem in question. $ dd if=/dev/zero of=test bs=1024 count=1024 1024+0 records in 1024+0 records out $ stat test File: `test' Size: 1048576 Blocks: 2056 IO Block: 32768 regular file Device: 26h/38d Inode: 15119606 Links: 1 Access: (0644/-rw-r--r--) Uid: (10059/ qwv684) Gid: (10001/ma29cu01) Access: 2007-05-14 22:48:01.058211000 -0400 Modify: 2007-05-14 22:57:28.468235000 -0400 Change: 2007-05-14 22:57:28.468235000 -0400 $ gzip test $ stat test.gz File: `test.gz' Size: 1056 Blocks: 8 IO Block: 32768 regular file Device: 26h/38d Inode: 6176375 Links: 1 Access: (0644/-rw-r--r--) Uid: (10059/ qwv684) Gid: (10001/ma29cu01) Access: 2007-05-14 22:48:01.000000000 -0400 Modify: 2007-05-14 22:57:28.000000000 -0400 Change: 2007-05-14 22:57:49.431252000 -0400 I will give .LOW_RESOLUTION_TIME a try. Is there a way to make this the default, rather than specifying it for every single one of my targets? Thanks, Dave _______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
