Back out one of the changes in log.c revision 1.62, and always send errors

[rsync/rsync.git] / rsync.yo

diff --git a/rsync.yo b/rsync.yo
index 6e65986..43edd8f 100644 (file)
--- a/rsync.yo
+++ b/rsync.yo
@@ -1,5 +1,5 @@
 mailto(rsync-bugs@samba.org)
 mailto(rsync-bugs@samba.org)

-manpage(rsync)(1)(25 Jan 2002)()()
+manpage(rsync)(1)(26 Jan 2003)()()

 manpagename(rsync)(faster, flexible replacement for rcp)
 manpagesynopsis()
 
 manpagename(rsync)(faster, flexible replacement for rcp)
 manpagesynopsis()
 


@@ -25,7 +25,7 @@ greatly speed up file transfers when the destination file already
 exists.
 
 The rsync remote-update protocol allows rsync to transfer just the
 exists.
 
 The rsync remote-update protocol allows rsync to transfer just the

-differences between two sets of files across the network link, using
+differences between two sets of files across the network connection, using

 an efficient checksum-search algorithm described in the technical
 report that accompanies this package.
 
 an efficient checksum-search algorithm described in the technical
 report that accompanies this package.
 


@@ -251,7 +251,7 @@ files and mail folders, I use a cron job that runs
 
 quote(rsync -Cavz . arvidsjaur:backup)
 
 
 quote(rsync -Cavz . arvidsjaur:backup)
 

-each night over a PPP link to a duplicate directory on my machine
+each night over a PPP connection to a duplicate directory on my machine

 "arvidsjaur".
 
 To synchronize my samba source trees I use the following Makefile
 "arvidsjaur".
 
 To synchronize my samba source trees I use the following Makefile


@@ -266,7 +266,7 @@ quote(      get:nl()
       sync: get put)
 
 this allows me to sync with a CVS directory at the other end of the
       sync: get put)
 
 this allows me to sync with a CVS directory at the other end of the

-link. I then do cvs operations on the remote machine, which saves a
+connection. I then do cvs operations on the remote machine, which saves a

 lot of time as the remote cvs protocol isn't very efficient.
 
 I mirror a directory between my "old" and "new" ftp sites with the
 lot of time as the remote cvs protocol isn't very efficient.
 
 I mirror a directory between my "old" and "new" ftp sites with the


@@ -396,8 +396,8 @@ dit(bf(--modify-window)) When comparing two timestamps rsync treats
 the timestamps as being equal if they are within the value of
 modify_window. This is normally zero, but you may find it useful to
 set this to a larger value in some situations. In particular, when
 the timestamps as being equal if they are within the value of
 modify_window. This is normally zero, but you may find it useful to
 set this to a larger value in some situations. In particular, when

-transferring to/from FAT filesystems which cannot represent times with
-a 1 second resolution this option is useful.
+transferring to Windows FAT filesystems which cannot represent times
+with a 1 second resolution --modify-window=1 is useful.

 
 dit(bf(-c, --checksum)) This forces the sender to checksum all files using
 a 128-bit MD4 checksum before transfer. The checksum is then
 
 dit(bf(-c, --checksum)) This forces the sender to checksum all files using
 a 128-bit MD4 checksum before transfer. The checksum is then


@@ -657,7 +657,7 @@ the bf(cvs(1)) manual for more information.
 dit(bf(--csum-length=LENGTH)) By default the primary checksum used in
 rsync is a very strong 16 byte MD4 checksum. In most cases you will
 find that a truncated version of this checksum is quite efficient, and
 dit(bf(--csum-length=LENGTH)) By default the primary checksum used in
 rsync is a very strong 16 byte MD4 checksum. In most cases you will
 find that a truncated version of this checksum is quite efficient, and

-this will decrease the size of the checksum data sent over the link,
+this will decrease the size of the checksum data sent over the connection,

 making things faster. 
 
 You can choose the number of bytes in the truncated checksum using the
 making things faster. 
 
 You can choose the number of bytes in the truncated checksum using the


@@ -698,7 +698,7 @@ linked.
 
 dit(bf(-z, --compress)) With this option, rsync compresses any data from
 the files that it sends to the destination machine.  This
 
 dit(bf(-z, --compress)) With this option, rsync compresses any data from
 the files that it sends to the destination machine.  This

-option is useful on slow links.  The compression method used is the
+option is useful on slow connections.  The compression method used is the

 same method that gzip uses.
 
 Note this this option typically achieves better compression ratios
 same method that gzip uses.
 
 Note this this option typically achieves better compression ratios


@@ -1110,16 +1110,17 @@ manpagebugs()
 
 times are transferred as unix time_t values
 
 
 times are transferred as unix time_t values
 

+When transferring to FAT filesystmes rsync may resync
+unmodified files.
+See the comments on the --modify-window option.
+

 file permissions, devices etc are transferred as native numerical
 values
 
 see also the comments on the --delete option
 
 file permissions, devices etc are transferred as native numerical
 values
 
 see also the comments on the --delete option
 

-Please report bugs! The rsync bug tracking system is online at
-url(http://rsync.samba.org/rsync/)(http://rsync.samba.org/rsync/)
-
-manpagesection(VERSION)
-This man page is current for version 2.0 of rsync
+Please report bugs! See the website at
+url(http://rsync.samba.org/)(http://rsync.samba.org/)

 
 manpagesection(CREDITS)
 
 
 manpagesection(CREDITS)