Displaying 2 results from an estimated 2 matches for "1321175".
Did you mean:
1321176
2016 Jan 25
0
[Bug 11521] rsync does not use high-resolution timestamps to determine file differences
...tch? Not just an optimization, but a change in
the way --link-dest might work. Observe:
22:57:22 ~$ mkdir T
22:57:25 ~$ cd T
22:57:26 ~/T$ mkdir 1 2 3 4 5 6
22:57:30 ~/T$ lat() { ls -alF -i --full-time "$@"; }
22:57:49 ~/T$ touch 1/foo
22:57:53 ~/T$ ln 1/foo 1/bar
22:57:56 ~/T$ lat */*
1321175 -rw-r--r-- 2 user user 0 2016-01-24 22:57:53.013689572 -0500 1/bar
1321175 -rw-r--r-- 2 user user 0 2016-01-24 22:57:53.013689572 -0500 1/foo
22:57:59 ~/T$ rsync -aviH 1/ 2/
sending incremental file list
.d..t...... ./
>f+++++++++ foo
hf+++++++++ bar => foo
sent 139 bytes received 53 bytes...
2014 Dec 25
8
[PATCH] Consider nanoseconds when quick-checking for unchanged files
On systems using nanoseconds differences should be taken into consideration.
--- a/generator.c 2014-06-14 01:05:08.000000000 +0200
+++ b/generator.c 2014-12-25 11:19:54.000000000 +0100
@@ -588,7 +588,13 @@
if (ignore_times)
return 0;
- return cmp_time(st->st_mtime, file->modtime) == 0;
+ return cmp_time(st->st_mtime, file->modtime) == 0
+#ifdef ST_MTIME_NSEC
+ ?