[BACK]Return to rsync.yo CVS log [TXT] [DIR] Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / rsync

Diff for /embedaddon/rsync/rsync.yo between versions 1.1.1.2 and 1.1.1.3

version 1.1.1.2, 2013/10/14 07:51:14 version 1.1.1.3, 2016/11/01 09:54:32
Line 1 Line 1
 mailto(rsync-bugs@samba.org)  mailto(rsync-bugs@samba.org)
manpage(rsync)(1)(28 Sep 2013)()()manpage(rsync)(1)(21 Dec 2015)()()
 manpagename(rsync)(a fast, versatile, remote (and local) file-copying tool)  manpagename(rsync)(a fast, versatile, remote (and local) file-copying tool)
 manpagesynopsis()  manpagesynopsis()
   
Line 103  This would transfer all files matching the pattern *.c Line 103  This would transfer all files matching the pattern *.c
 current directory to the directory src on the machine foo. If any of  current directory to the directory src on the machine foo. If any of
 the files already exist on the remote system then the rsync  the files already exist on the remote system then the rsync
 remote-update protocol is used to update the file by sending only the  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).
   
 quote(tt(rsync -avz foo:src/bar /data/tmp))  quote(tt(rsync -avz foo:src/bar /data/tmp))
   
Line 513  fine-grained settings override the implied settings of Line 516  fine-grained settings override the implied settings of
 bf(--info) and bf(--debug) have a way to ask for help that tells you  bf(--info) and bf(--debug) have a way to ask for help that tells you
 exactly what flags are set for each increase in verbosity.  exactly what flags are set for each increase in verbosity.
   
   However, do keep in mind that a daemon's "max verbosity" 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 bf(-vv) will be downgraded to the
   bf(-vv) level in the daemon's logging.
   
 dit(bf(--info=FLAGS))  dit(bf(--info=FLAGS))
 This option lets you have fine-grained control over the  This option lets you have fine-grained control over the
 information  information
Line 534  information on what is output and when. Line 543  information on what is output and when.
 This option was added to 3.1.0, so an older rsync on the server side might  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  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).  to be send to the server and the server was too old to understand them).
   See also the "max verbosity" caveat above when dealing with a daemon.
   
 dit(bf(--debug=FLAGS))  dit(bf(--debug=FLAGS))
 This option lets you have fine-grained control over the debug  This option lets you have fine-grained control over the debug
Line 554  specified, especially those pertaining to I/O and buff Line 564  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  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  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).  to be send to the server and the server was too old to understand them).
   See also the "max verbosity" caveat above when dealing with a daemon.
   
 dit(bf(--msgs2stderr)) This option changes rsync to send all its output  dit(bf(--msgs2stderr)) This option changes rsync to send all its output
 directly to stderr rather than to send messages to the client side via the  directly to stderr rather than to send messages to the client side via the
 protocol (which normally outputs info messages via stdout).  This is mainly  protocol (which normally outputs info messages via stdout).  This is mainly
 intended for debugging in order to avoid changing the data sent via the  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.  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 sendThe option does not affect the remote side of a transfer without using
 bf(--remote-option) -- e.g. bf(-M--msgs2stderr).
 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  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 bf(--no-detach)  debugging using this option, you should start up a daemon using bf(--no-detach)
 so that you can see the stderr output on the daemon side.  so that you can see the stderr output on the daemon side.
Line 789  the destination and have a modified time that is newer Line 802  the destination and have a modified time that is newer
 file.  (If an existing destination file has a modification time equal to the  file.  (If an existing destination file has a modification time equal to the
 source file's, it will be updated if the sizes are different.)  source file's, it will be updated if the sizes are different.)
   
Note that this does not affect the copying of symlinks or other specialNote 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  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  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  date is on the objects.  In other words, if the source has a directory
Line 853  Implies bf(--inplace), Line 866  Implies bf(--inplace),
 but does not conflict with bf(--sparse) (since it is always extending a  but does not conflict with bf(--sparse) (since it is always extending a
 file's length).  file's length).
   
   The use of bf(--append) can be dangerous if you aren'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.
   
 dit(bf(--append-verify)) This works just like the bf(--append) option, but  dit(bf(--append-verify)) This works just like the bf(--append) option, but
 the existing data on the receiving side is included in the full-file  the existing data on the receiving side is included in the full-file
 checksum verification step, which will cause a file to be resent if the  checksum verification step, which will cause a file to be resent if the
Line 1167  it is preserving modification times (see bf(--times)). Line 1185  it is preserving modification times (see bf(--times)).
 the directories on the receiving side, it is a good idea to use bf(-O).  the directories on the receiving side, it is a good idea to use bf(-O).
 This option is inferred if you use bf(--backup) without bf(--backup-dir).  This option is inferred if you use bf(--backup) without bf(--backup-dir).
   
   This option also has the side-effect of avoiding early creation of directories
   in incremental recursion copies.  The default bf(--inc-recursive) 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't have accurate mode, mtime, or ownership, the use of this
   option can help when someone wants to avoid these partially-finished
   directories.
   
 dit(bf(-J, --omit-link-times)) This tells rsync to omit symlinks when  dit(bf(-J, --omit-link-times)) This tells rsync to omit symlinks when
 it is preserving modification times (see bf(--times)).  it is preserving modification times (see bf(--times)).
   
Line 1726  dit(bf(-T, --temp-dir=DIR)) This option instructs rsyn Line 1755  dit(bf(-T, --temp-dir=DIR)) This option instructs rsyn
 scratch directory when creating temporary copies of the files transferred  scratch directory when creating temporary copies of the files transferred
 on the receiving side.  The default behavior is to create each temporary  on the receiving side.  The default behavior is to create each temporary
 file in the same directory as the associated destination file.  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).
   
 This option is most often used when the receiving disk partition does not  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.  have enough free space to hold a copy of the largest file in the transfer.
Line 1856  being transmitted -- something that is useful over a s Line 1888  being transmitted -- something that is useful over a s
 Note that this option typically achieves better compression ratios than can  Note that this option typically achieves better compression ratios than can
 be achieved by using a compressing remote shell or a compressing transport  be achieved by using a compressing remote shell or a compressing transport
 because it takes advantage of the implicit information in the matching data  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 bf(-z) option, but only if both sides are at least version 3.1.1.
   
   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.
   
   The client rsync requests new-style compression on the server via the
   bf(--new-compress) option, so if you see that option rejected it means that
   the server is not new enough to support bf(-zz).  Rsync also accepts the
   bf(--old-compress) option for a future time when new-style compression
   becomes the default.
   
 See the bf(--skip-compress) option for the default list of file suffixes  See the bf(--skip-compress) option for the default list of file suffixes
 that will not be compressed.  that will not be compressed.
   
Line 2411  transfer that may be interrupted. Line 2456  transfer that may be interrupted.
   
 There is also a bf(--info=progress2) option that outputs statistics based  There is also a bf(--info=progress2) option that outputs statistics based
 on the whole transfer, rather than individual files.  Use this flag without  on the whole transfer, rather than individual files.  Use this flag without
outputting a filename (e.g. avoid bf(-v) or specify bf(--info=name0) if yououtputting a filename (e.g. avoid bf(-v) or specify bf(--info=name0)) if you
 want to see how the transfer is doing without scrolling the screen with a  want to see how the transfer is doing without scrolling the screen with a
 lot of names.  (You don't need to specify the bf(--progress) option in  lot of names.  (You don't need to specify the bf(--progress) option in
 order to use bf(--info=progress2).)  order to use bf(--info=progress2).)
Line 2743  itemization( Line 2788  itemization(
   it() a '[' introduces a character class, such as [a-z] or [[:alpha:]].    it() a '[' introduces a character class, such as [a-z] or [[:alpha:]].
   it() in a wildcard pattern, a backslash can be used to escape a wildcard    it() in a wildcard pattern, a backslash can be used to escape a wildcard
   character, but it is matched literally when no wildcards are present.    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 "foo\bar" (which matches the backslash) you
     would need to use "foo\\bar*" to avoid the "\b" becoming just "b".
   it() if the pattern contains a / (not counting a trailing /) or a "**",    it() if the pattern contains a / (not counting a trailing /) or a "**",
   then it is matched against the full pathname, including any leading    then it is matched against the full pathname, including any leading
   directories. If the pattern doesn't contain a / or a "**", then it is    directories. If the pattern doesn't contain a / or a "**", then it is
Line 3361  url(http://rsync.samba.org/)(http://rsync.samba.org/) Line 3410  url(http://rsync.samba.org/)(http://rsync.samba.org/)
   
 manpagesection(VERSION)  manpagesection(VERSION)
   
This man page is current for version 3.1.0 of rsync.This man page is current for version 3.1.2 of rsync.
   
 manpagesection(INTERNAL OPTIONS)  manpagesection(INTERNAL OPTIONS)
   
Removed from v.1.1.1.2  
changed lines
  Added in v.1.1.1.3

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>