summaryrefslogtreecommitdiff
path: root/rsync.yo
diff options
context:
space:
mode:
authorWayne Davison <wayned@samba.org>2011-02-20 23:29:00 -0800
committerWayne Davison <wayned@samba.org>2011-02-20 23:30:53 -0800
commit3bd9f51917ed5718275c6132006be155239a0550 (patch)
tree1ea1cbb8a859cb01cdfdbf3cee1d76f99c11c940 /rsync.yo
parent86e90c58f46dd13254e0dc38b9eea37589ace457 (diff)
downloadrsync-3bd9f51917ed5718275c6132006be155239a0550.tar.gz
rsync-3bd9f51917ed5718275c6132006be155239a0550.tar.bz2
rsync-3bd9f51917ed5718275c6132006be155239a0550.zip
Improve some hard-link caveats in the manpage.
Diffstat (limited to 'rsync.yo')
-rw-r--r--rsync.yo13
1 files changed, 7 insertions, 6 deletions
diff --git a/rsync.yo b/rsync.yo
index 65daed54..5c11d956 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -943,13 +943,14 @@ destination exactly matches that on the source. Cases in which the
destination may end up with extra hard links include the following:
quote(itemization(
- it() If the destination already contains hard links, rsync will not break
- them explicitly. However, if one or more of the paths have content
- differences, the normal file-update process will break those links, unless
- you are using the bf(--inplace) option.
+ it() If the destination contains extraneous hard-linked files, rsync will not
+ break them explicitly. However, if one or more of the paths have content
+ differences, the normal file-update process will break those extra links
+ (unless you are using the bf(--inplace) option).
it() If you specify a bf(--link-dest) directory that contains hard links,
- rsync may use the same bf(--link-dest) file multiple times via several of
- its paths.
+ the linking of the destination files against the bf(--link-dest) files can
+ cause some paths in the destination to become linked together due to the
+ bf(--link-dest) associations.
))
Note that rsync can only detect hard links between files that are inside