--- embedaddon/rsync/rsync.1	2013/10/14 07:51:14	1.1.1.2
+++ embedaddon/rsync/rsync.1	2016/11/01 09:54:32	1.1.1.3
@@ -1,4 +1,4 @@
-.TH "rsync" "1" "28 Sep 2013" "" ""
+.TH "rsync" "1" "21 Dec 2015" "" ""
 .SH "NAME"
 rsync \- a fast, versatile, remote (and local) file\-copying tool
 .SH "SYNOPSIS"
@@ -120,7 +120,10 @@ This would transfer all files matching the pattern *.c
 current directory to the directory src on the machine foo. If any of
 the files already exist on the remote system then the rsync
 remote\-update protocol is used to update the file by sending only the
-differences. See the tech report for details.
+differences in the data.  Note that the expansion of wildcards on the
+commandline (*.c) into a list of files is handled by the shell before
+it runs rsync and not by rsync itself (exactly the same as all other
+posix\-style programs).
 .PP 
 .RS 
 \f(CWrsync \-avz foo:src/bar /data/tmp\fP
@@ -598,6 +601,12 @@ fine\-grained settings override the implied settings o
 \fB\-\-info\fP and \fB\-\-debug\fP have a way to ask for help that tells you
 exactly what flags are set for each increase in verbosity.
 .IP 
+However, do keep in mind that a daemon\(cq\&s \(dq\&max verbosity\(dq\& setting will limit how
+high of a level the various individual flags can be set on the daemon side.
+For instance, if the max is 2, then any info and/or debug flag that is set to
+a higher value than what would be set by \fB\-vv\fP will be downgraded to the
+\fB\-vv\fP level in the daemon\(cq\&s logging.
+.IP 
 .IP "\fB\-\-info=FLAGS\fP"
 This option lets you have fine\-grained control over the
 information
@@ -622,6 +631,7 @@ information on what is output and when.
 This option was added to 3.1.0, so an older rsync on the server side might
 reject your attempts at fine\-grained control (if one or more flags needed
 to be send to the server and the server was too old to understand them).
+See also the \(dq\&max verbosity\(dq\& caveat above when dealing with a daemon.
 .IP 
 .IP "\fB\-\-debug=FLAGS\fP"
 This option lets you have fine\-grained control over the debug
@@ -645,6 +655,7 @@ specified, especially those pertaining to I/O and buff
 This option was added to 3.1.0, so an older rsync on the server side might
 reject your attempts at fine\-grained control (if one or more flags needed
 to be send to the server and the server was too old to understand them).
+See also the \(dq\&max verbosity\(dq\& caveat above when dealing with a daemon.
 .IP 
 .IP "\fB\-\-msgs2stderr\fP"
 This option changes rsync to send all its output
@@ -652,7 +663,9 @@ directly to stderr rather than to send messages to the
 protocol (which normally outputs info messages via stdout).  This is mainly
 intended for debugging in order to avoid changing the data sent via the
 protocol, since the extra protocol data can change what is being tested.
-Keep in mind that a daemon connection does not have a stderr channel to send
+The option does not affect the remote side of a transfer without using
+\fB\-\-remote\-option\fP \-\- e.g. \fB\-M\-\-msgs2stderr\fP.
+Also keep in mind that a daemon connection does not have a stderr channel to send
 messages back to the client side, so if you are doing any daemon\-transfer
 debugging using this option, you should start up a daemon using \fB\-\-no\-detach\fP
 so that you can see the stderr output on the daemon side.
@@ -910,7 +923,7 @@ the destination and have a modified time that is newer
 file.  (If an existing destination file has a modification time equal to the
 source file\(cq\&s, it will be updated if the sizes are different.)
 .IP 
-Note that this does not affect the copying of symlinks or other special
+Note that this does not affect the copying of dirs, symlinks, or other special
 files.  Also, a difference of file format between the sender and receiver
 is always considered to be important enough for an update, no matter what
 date is on the objects.  In other words, if the source has a directory
@@ -982,6 +995,11 @@ Implies \fB\-\-inplace\fP,
 but does not conflict with \fB\-\-sparse\fP (since it is always extending a
 file\(cq\&s length).
 .IP 
+The use of \fB\-\-append\fP can be dangerous if you aren\(cq\&t 100% sure that the files
+that are longer have only grown by the appending of data onto the end.  You
+should thus use include/exclude/filter rules to ensure that such a transfer is
+only affecting files that you know to be growing via appended data.
+.IP 
 .IP "\fB\-\-append\-verify\fP"
 This works just like the \fB\-\-append\fP option, but
 the existing data on the receiving side is included in the full\-file
@@ -1342,6 +1360,17 @@ it is preserving modification times (see \fB\-\-times\
 the directories on the receiving side, it is a good idea to use \fB\-O\fP.
 This option is inferred if you use \fB\-\-backup\fP without \fB\-\-backup\-dir\fP.
 .IP 
+This option also has the side\-effect of avoiding early creation of directories
+in incremental recursion copies.  The default \fB\-\-inc\-recursive\fP copying
+normally does an early\-create pass of all the sub\-directories in a parent
+directory in order for it to be able to then set the modify time of the parent
+directory right away (without having to delay that until a bunch of recursive
+copying has finished).  This early\-create idiom is not necessary if directory
+modify times are not being preserved, so it is skipped.  Since early\-create
+directories don\(cq\&t have accurate mode, mtime, or ownership, the use of this
+option can help when someone wants to avoid these partially\-finished
+directories.
+.IP 
 .IP "\fB\-J, \-\-omit\-link\-times\fP"
 This tells rsync to omit symlinks when
 it is preserving modification times (see \fB\-\-times\fP).
@@ -1977,6 +2006,9 @@ This option instructs rsync to use DIR as a
 scratch directory when creating temporary copies of the files transferred
 on the receiving side.  The default behavior is to create each temporary
 file in the same directory as the associated destination file.
+Beginning with rsync 3.1.1, the temp\-file names inside the specified DIR will
+not be prefixed with an extra dot (though they will still have a random suffix
+added).
 .IP 
 This option is most often used when the receiving disk partition does not
 have enough free space to hold a copy of the largest file in the transfer.
@@ -2115,8 +2147,21 @@ being transmitted \-\- something that is useful over a
 Note that this option typically achieves better compression ratios than can
 be achieved by using a compressing remote shell or a compressing transport
 because it takes advantage of the implicit information in the matching data
-blocks that are not explicitly sent over the connection.
+blocks that are not explicitly sent over the connection.  This matching\-data
+compression comes at a cost of CPU, though, and can be disabled by repeating
+the \fB\-z\fP option, but only if both sides are at least version 3.1.1.
 .IP 
+Note that if your version of rsync was compiled with an external zlib (instead
+of the zlib that comes packaged with rsync) then it will not support the
+old\-style compression, only the new\-style (repeated\-option) compression.  In
+the future this new\-style compression will likely become the default.
+.IP 
+The client rsync requests new\-style compression on the server via the
+\fB\-\-new\-compress\fP option, so if you see that option rejected it means that
+the server is not new enough to support \fB\-zz\fP.  Rsync also accepts the
+\fB\-\-old\-compress\fP option for a future time when new\-style compression
+becomes the default.
+.IP 
 See the \fB\-\-skip\-compress\fP option for the default list of file suffixes
 that will not be compressed.
 .IP 
@@ -2753,7 +2798,7 @@ transfer that may be interrupted.
 .IP 
 There is also a \fB\-\-info=progress2\fP option that outputs statistics based
 on the whole transfer, rather than individual files.  Use this flag without
-outputting a filename (e.g. avoid \fB\-v\fP or specify \fB\-\-info=name0\fP if you
+outputting a filename (e.g. avoid \fB\-v\fP or specify \fB\-\-info=name0\fP) if you
 want to see how the transfer is doing without scrolling the screen with a
 lot of names.  (You don\(cq\&t need to specify the \fB\-\-progress\fP option in
 order to use \fB\-\-info=progress2\fP.)
@@ -3138,6 +3183,10 @@ a \(cq\&[\(cq\& introduces a character class, such as 
 .IP o 
 in a wildcard pattern, a backslash can be used to escape a wildcard
 character, but it is matched literally when no wildcards are present.
+This means that there is an extra level of backslash removal when a
+pattern contains wildcard characters compared to a pattern that has none.
+e.g. if you add a wildcard to \(dq\&foo\ebar\(dq\& (which matches the backslash) you
+would need to use \(dq\&foo\e\ebar*\(dq\& to avoid the \(dq\&\eb\(dq\& becoming just \(dq\&b\(dq\&.
 .IP o 
 if the pattern contains a / (not counting a trailing /) or a \(dq\&**\(dq\&,
 then it is matched against the full pathname, including any leading
@@ -3904,7 +3953,7 @@ http://rsync.samba.org/
 .SH "VERSION"
 
 .PP 
-This man page is current for version 3.1.0 of rsync.
+This man page is current for version 3.1.2 of rsync.
 .PP 
 .SH "INTERNAL OPTIONS"