[SCM] The rsync repository. - branch master updated

Rsync CVS commit messages rsync-cvs at lists.samba.org
Sat Jan 1 19:21:26 MST 2011

The branch, master has been updated
       via  8030518 Clarify incremental recursion's effect on --hard-link.
       via  e630fd1 Some --inplace manpage enhancements.
      from  d3f5c62 Avoid directory permission issues with --fake-super. Fixes bug 7070.


- Log -----------------------------------------------------------------
commit 8030518dd019a66fb2d6c2e7c9d0de32e3130fe6
Author: Wayne Davison <wayned at samba.org>
Date:   Sat Jan 1 18:20:09 2011 -0800

    Clarify incremental recursion's effect on --hard-link.

commit e630fd11869ca2824154ee585ab77059b91ca0ac
Author: Wayne Davison <wayned at samba.org>
Date:   Sat Jan 1 18:16:49 2011 -0800

    Some --inplace manpage enhancements.


Summary of changes:
 rsync.yo |   12 +++++++++---
 1 files changed, 9 insertions(+), 3 deletions(-)

Changeset truncated at 500 lines:

diff --git a/rsync.yo b/rsync.yo
index 0ad14f3..456bd4f 100644
--- a/rsync.yo
+++ b/rsync.yo
@@ -781,7 +781,9 @@ quote(itemization(
   it() The file's data will be in an inconsistent state during the transfer
   and will be left that way if the transfer is interrupted or if an update
-  it() A file that does not have write permissions cannot be updated.
+  it() A file that rsync cannot write to cannot be updated. While a super user
+  can update any file, a normal user needs to be granted write permission for
+  the open of the file for writing to be successful.
   it() The efficiency of rsync's delta-transfer algorithm may be reduced if
   some data in the destination file is overwritten before it can be copied to
   a position later in the file.  This does not apply if you use bf(--backup),
@@ -794,7 +796,8 @@ accessed by others, so be careful when choosing to use this for a copy.
 This option is useful for transferring large files with block-based changes
 or appended data, and also on systems that are disk bound, not network
+bound.  It can also help keep a copy-on-write filesystem snapshot from
+diverging the entire contents of a file that only has minor changes.
 The option implies bf(--partial) (since an interrupted transfer does not delete
 the file), but conflicts with bf(--partial-dir) and bf(--delay-updates).
@@ -960,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
-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

The rsync repository.

More information about the rsync-cvs mailing list