From: Wayne Davison Date: Mon, 21 Feb 2011 07:29:00 +0000 (-0800) Subject: Improve some hard-link caveats in the manpage. X-Git-Tag: v3.1.0pre1~151 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3bd9f51917ed5718275c6132006be155239a0550;p=thirdparty%2Frsync.git Improve some hard-link caveats in the manpage. --- 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