Matt McCutchen's Web Site
/
rsync
/
rsync.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
e630fd1
)
Clarify incremental recursion's effect on --hard-link.
author
Wayne Davison
<wayned@samba.org>
Sun, 2 Jan 2011 02:20:09 +0000
(18:20 -0800)
committer
Wayne Davison
<wayned@samba.org>
Sun, 2 Jan 2011 02:21:40 +0000
(18:21 -0800)
rsync.yo
patch
|
blob
|
blame
|
history
diff --git
a/rsync.yo
b/rsync.yo
index
610cc9d
..
456bd4f
100644
(file)
--- a/
rsync.yo
+++ b/
rsync.yo
@@
-963,7
+963,10
@@
see the bf(--inplace) option for more caveats).
If incremental recursion is active (see bf(--recursive)), rsync may transfer
a missing hard-linked file before it finds that another link for that contents
exists elsewhere in the hierarchy. This does not affect the accuracy of
If incremental recursion is active (see bf(--recursive)), rsync may transfer
a missing hard-linked file before it finds that another link for that contents
exists elsewhere in the hierarchy. This does not affect the accuracy of
-the transfer, just its efficiency. One way to avoid this is to disable
+the transfer (i.e. which files are hard-linked together), just its efficiency
+(i.e. copying the data for a new, early copy of a hard-linked file that could
+have been found later in the transfer in another member of the hard-linked
+set of files). One way to avoid this inefficiency is to disable
incremental recursion using the bf(--no-inc-recursive) option.
dit(bf(-p, --perms)) This option causes the receiving rsync to set the
incremental recursion using the bf(--no-inc-recursive) option.
dit(bf(-p, --perms)) This option causes the receiving rsync to set the