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 in the data. Note that the
-expansion of wildcards on the commandline (`*.c`) into a list of files is
+expansion of wildcards on the command-line (`*.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).
+same as all other Posix-style programs).
> rsync -avz foo:src/bar /data/tmp
detailed description below for a complete description.
[comment]: # (help-rsync.h)
-[comment]: # (Keep these short enough that they'll be under 80 chars when indented by 8 chars.)
+[comment]: # (Keep these short enough that they'll be under 80 chars when indented by 7 chars.)
```
--verbose, -v increase verbosity
--info=FLAGS fine-grained informational verbosity
--debug=FLAGS fine-grained debug verbosity
---msgs2stderr output messages directly to stderr
+--stderr=e|a|c change stderr output mode (default: errors)
--quiet, -q suppress non-error messages
--no-motd suppress daemon-mode MOTD
--checksum, -c skip based on checksum, not mod-time & size
---archive, -a archive mode; equals -rlptgoD (no -H,-A,-X)
+--archive, -a archive mode is -rlptgoD (no -A,-X,-U,-N,-H)
--no-OPTION turn off an implied OPTION (e.g. --no-D)
--recursive, -r recurse into directories
--relative, -R use relative path names
--append append data onto shorter files
--append-verify --append w/old data in file checksum
--dirs, -d transfer directories without recursing
+--mkpath create the destination's path component
--links, -l copy symlinks as symlinks
--copy-links, -L transform symlink into referent file/dir
--copy-unsafe-links only "unsafe" symlinks are transformed
--times, -t preserve modification times
--atimes, -U preserve access (use) times
--open-noatime avoid changing the atime on opened files
+--crtimes, -N preserve create times (newness)
--omit-dir-times, -O omit directories from --times
--omit-link-times, -J omit symlinks from --times
--super receiver attempts super-user activities
--early-input=FILE use FILE for daemon's early exec input
--list-only list the files instead of copying them
--bwlimit=RATE limit socket I/O bandwidth
+--stop-after=MINS Stop rsync after MINS minutes have elapsed
+--stop-at=y-m-dTh:m Stop rsync at the specified point in time
--write-batch=FILE write a batched update to FILE
--only-write-batch=FILE like --write-batch but w/o updating dest
--read-batch=FILE read a batched update from FILE
> rsync -avvv --debug=none src/ dest/
> rsync -avA --del --debug=del2,acl src/ dest/
- Note that some debug messages will only be output when `--msgs2stderr` is
+ Note that some debug messages will only be output when `--stderr=all` is
specified, especially those pertaining to I/O and buffer debugging.
- Beginning in 3.2.0, this option is no longer auto-forwared to the server
+ Beginning in 3.2.0, this option is no longer auto-forwarded to the server
side in order to allow you to specify different debug values for each side
of the transfer, as well as to specify a new debug option that is only
present in one of the rsync versions. If you want to duplicate the same
> rsync -aiv {-M,}--debug=del2 src/ dest/
-0. `--msgs2stderr`
-
- This option changes rsync to send all its output directly to stderr rather
- than to send messages to the client side via the protocol. The protocol
- allows rsync to output normal messages via stdout and errors via stderr,
- but it can delay messages behind a slew of data.
-
- One case where this is helpful is when sending really large files, since
- errors that happen on a remote receiver tend to get delayed until after the
- file's data is fully sent. It is also helpful for debugging, since it
- helps to avoid overpopulating the protocol data with extra message data.
-
- The option does not affect the remote side of a transfer without using
- `--remote-option`, e.g. `-M--msgs2stderr` or `{-M,}--msgs2stderr`.
-
- Also keep in mind that connecting to a normal (non-remote-shell) daemon
- does not have a stderr channel to send messages back to the client side, so
- a modern rsync only allows the option on a remote-shell-run daemon.
-
- This option has the side-effect of making stderr output get line-buffered
- so that the merging of the output of 3 programs happens in a more readable
- manner.
+0. `--stderr=errors|all|client`
+
+ This option controls which processes output to stderr and if info messages
+ are also changed to stderr. The mode strings can be abbreviated, so feel
+ free to use a single letter value. The 3 possible choices are:
+
+ - `errors` - (the default) causes all the rsync processes to send an
+ error directly to stderr, even if the process is on the remote side of
+ the transfer. Info messages are sent to the client side via the protocol
+ stream. If stderr is not available (i.e. when directly connecting with a
+ daemon via a socket) errors fall back to being sent via the protocol
+ stream.
+
+ - `all` - causes all rsync messages (info and error) to get written
+ directly to stderr from all (possible) processes. This causes stderr to
+ become line-buffered (instead of raw) and eliminates the ability to
+ divide up the info and error messages by file handle. For those doing
+ debugging or using several levels of verbosity, this option can help to
+ avoid clogging up the transfer stream (which should prevent any chance of
+ a deadlock bug hanging things up). It also allows `--debug` to enable
+ some extra I/O related messages.
+
+ - `client` - causes all rsync messages to be sent to the client side
+ via the protocol stream. One client process outputs all messages, with
+ errors on stderr and info messages on stdout. This **was** the default
+ in older rsync versions, but can cause error delays when a lot of
+ transfer data is ahead of the messages. If you're pushing files to an
+ older rsync, you may want to use `--stderr=all` since that idiom has
+ been around for several releases.
+
+ This option was added in rsync 3.2.3. This version also began the
+ forwarding of a non-default setting to the remote side, though rsync uses
+ the backward-compatible options `--msgs2stderr` and `--no-msgs2stderr` to
+ represent the `all` and `client` settings, respectively. A newer rsync
+ will continue to accept these older option names to maintain compatibility.
0. `--quiet`, `-q`
the same modification timestamp. This option turns off this "quick check"
behavior, causing all files to be updated.
+ This option can be a little confusing compared to `--ignore-existing` and
+ `--ignore-non-existing` in that that they cause rsync to transfer fewer
+ files, while this option causes rsync to transfer more files.
+
0. `--size-only`
This modifies rsync's "quick check" algorithm for finding files that need
before-the-transfer "Does this file need to be updated?" check.
The checksum used is auto-negotiated between the client and the server, but
- can be overridden using either the `--checksum-choice` option or an
+ can be overridden using either the `--checksum-choice` (`--cc`) option or an
environment variable that is discussed in that option's section.
0. `--archive`, `-a`
This is equivalent to `-rlptgoD`. It is a quick way of saying you want
- recursion and want to preserve almost everything (with `-H` being a notable
- omission). The only exception to the above equivalence is when
- `--files-from` is specified, in which case `-r` is not implied.
+ recursion and want to preserve almost everything. Be aware that it does
+ **not** include preserving ACLs (`-A`), xattrs (`-X`), atimes (`-U`),
+ crtimes (`-N`), nor the finding and preserving of hardlinks (`-H`).
- Note that `-a` **does not preserve hardlinks**, because finding
- multiply-linked files is expensive. You must separately specify `-H`.
+ The only exception to the above equivalence is when
+ `--files-from` is specified, in which case `-r` is not implied.
0. `--no-OPTION`
0. `--append`
- This causes rsync to update a file by appending data onto the end of the
- file, which presumes that the data that already exists on the receiving
- side is identical with the start of the file on the sending side. If a
- file needs to be transferred and its size on the receiver is the same or
- longer than the size on the sender, the file is skipped. This does not
- interfere with the updating of a file's non-content attributes (e.g.
- permissions, ownership, etc.) when the file does not need to be
- transferred, nor does it affect the updating of any non-regular files.
- Implies `--inplace`.
-
- The use of `--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.
+ This special copy mode only works to efficiently update files that are
+ known to be growing larger where any existing content on the receiving side
+ is also known to be the same as the content on the sender. The use of
+ `--append` **can be dangerous** if you aren't 100% sure that all the files
+ in the transfer are shared, growing files. You should thus use filter
+ rules to ensure that you weed out any files that do not fit this criteria.
+
+ Rsync updates these growing file in-place without verifying any of the
+ existing content in the file (it only verifies the content that it is
+ appending). Rsync skips any files that exist on the receiving side that
+ are not shorter than the associated file on the sending side (which means
+ that new files are trasnferred). It also skips any files whose size on the
+ sending side gets shorter during the send negotiations (rsync warns about a
+ "diminished" file when this happens).
+
+ This does not interfere with the updating of a file's non-content
+ attributes (e.g. permissions, ownership, etc.) when the file does not need
+ to be transferred, nor does it affect the updating of any directories or
+ non-regular files.
0. `--append-verify`
- This works just like the `--append` option, but 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 final verification step fails
- (rsync uses a normal, non-appending `--inplace` transfer for the resend).
- It otherwise has the exact same caveats for files that have not grown
- larger, so don't use this for a general copy.
+ This special copy mode works like `--append` except that all the data in
+ the file is included in the checksum verification (making it much less
+ efficient but also potentially safer). This option **can be dangerous** if
+ you aren't 100% sure that all the files in the transfer are shared, growing
+ files. See the `--append` option for more details.
Note: prior to rsync 3.0.0, the `--append` option worked like
`--append-verify`, so if you are interacting with an older rsync (or the
`--old-d`) that tells rsync to use a hack of `-r --exclude='/*/*'` to get
an older rsync to list a single directory without recursing.
+0. `--mkpath`
+
+ Create a missing path component of the destination arg. This allows rsync
+ to create multiple levels of missing destination dirs and to create a path
+ in which to put a single renamed file. Keep in mind that you'll need to
+ supply a trailing slash if you want the entire destination path to be
+ treated as a directory when copying a single arg (making rsync behave the
+ same way that it would if the path component of the destination had already
+ existed).
+
+ For example, the following creates a copy of file foo as bar in the sub/dir
+ directory, creating dirs "sub" and "sub/dir" if either do not yet exist:
+
+ > rsync -ai --mkpath foo sub/dir/bar
+
+ If you instead ran the following, it would have created file foo in the
+ sub/dir/bar directory:
+
+ > rsync -ai --mkpath foo sub/dir/bar/
+
0. `--links`, `-l`
When symlinks are encountered, recreate the symlink on the destination.
mounted to avoid updating the atime on read access even without the
O_NOATIME flag being set.
+0. `--crtimes`, `-N,`
+
+ This tells rsync to set the create times (newness) of the destination
+ files to the same value as the source files.
+
0. `--omit-dir-times`, `-O`
This tells rsync to omit directories when it is preserving modification
- `md4`
- `none`
- Run `rsync -V` to see the default checksum list compiled into your version
- (which may differ from the above list).
+ Run `rsync --version` to see the default checksum list compiled into your
+ version (which may differ from the list above).
If "none" is specified for the first (or only) name, the `--whole-file`
option is forced on and no checksum verification is performed on the
The default order can be customized by setting the environment variable
RSYNC_CHECKSUM_LIST to a space-separated list of acceptable checksum names.
- If the environment variable contains a "`&`" character, the string is
- separated into the "client list & server list" otherwise the same string
+ If the string contains a "`&`" character, it is separated into the "client
+ string & server string", otherwise the same string
applies to both. If the string (or string portion) contains no
non-whitespace characters, the default checksum list is used. This method
does not allow you to specify the transfer checksum separately from the
permissions on the hard-linked files). This does mean that this option is
only looking at the existing files in the destination hierarchy itself.
+ When `--info=skip2` is used rsync will output "FILENAME exists (INFO)"
+ messages where the INFO indicates one of "type change", "sum change"
+ (requires `-c`), "file change" (based on the quick check), "attr change",
+ or "uptodate". Using `--info=skip1` (which is also implied by `-vv`)
+ outputs the exists message without the INFO suffix.
+
0. `--remove-source-files`
This tells rsync to remove from the sending side the files (meaning
0. `--max-size=SIZE`
This tells rsync to avoid transferring any file that is larger than the
- specified SIZE. The SIZE value can be suffixed with a string to indicate a
- size multiplier, and may be a fractional value (e.g. `--max-size=1.5m`).
+ specified SIZE. A numeric value can be suffixed with a string to indicate
+ the numeric units or left unqualified to specify bytes. Feel free to use a
+ fractional value along with the units, such as `--max-size=1.5m`.
This option is a transfer rule, not an exclude, so it doesn't affect the
data that goes into the file-lists, and thus it doesn't affect deletions.
It just limits the files that the receiver requests to be transferred.
- The accepted suffix letters are: `B`, `K`, `G`, `T`, and `P` for bytes,
- kilobytes/kibibytes, megabytes/mebibytes, gigabytes/gibibytes,
- terabytes/tebibytes, and petabytes/pebibytes. If you use a single-char
- suffix or add-on "ib" to it (e.g. "G" or "GiB") then you get units that are
+ The first letter of a units string can be `B` (bytes), `K` (kilo), `M`
+ (mega), `G` (giga), `T` (tera), or `P` (peta). If the string is a single
+ char or has "ib" added to it (e.g. "G" or "GiB") then the units are
multiples of 1024. If you use a two-letter suffix that ends with a "B"
- (e.g. "kb") then you get units that are multiples of 1000. The suffix
+ (e.g. "kb") then you get units that are multiples of 1000. The string's
letters can be any mix of upper and lower-case that you want to use.
Finally, if the string ends with either "+1" or "-1", it is offset by one
- byte in the indicated direction. The largest possible value is `8192P-1`.
+ byte in the indicated direction. The largest possible value is usually
+ `8192P-1`.
Examples: `--max-size=1.5mb-1` is 1499999 bytes, and `--max-size=2g+1` is
2147483649 bytes.
See the `--max-size` option for a description of how SIZE can be specified.
The default suffix if none is given is bytes.
+ Beginning in 3.2.3, a value of 0 specifies no limit.
+
You can set a default value using the environment variable RSYNC_MAX_ALLOC
using the same SIZE values as supported by this option. If the remote
rsync doesn't understand the `--max-alloc` option, you can override an
fixed value. It is normally selected based on the size of each file being
updated. See the technical report for details.
+ Beginning in 3.2.3 the SIZE can be specified with a suffix as detailed in
+ the `--max-size` option. Older versions only accepted a byte count.
+
0. `--rsh=COMMAND`, `-e`
This option allows you to choose an alternative remote shell program to use
Rsync can also be configured (at build time) to have this option enabled by
default (with is overridden by both the environment and the command-line).
- Run `rsync -V` to check if this is the case, as it will display "default
- protect-args" or "optional protect-args" depending on how it was compiled.
+ Run `rsync --version` to check if this is the case, as it will display
+ "default protect-args" or "optional protect-args" depending on how it was
+ compiled.
This option will eventually become a new default setting at some
as-yet-undetermined point in the future.
has no permissions to change.
The following command does a local copy into the "dest/" dir as user "joe"
- (assumimg you've installed support/lsh into a dir on your $PATH):
+ (assuming you've installed support/lsh into a dir on your $PATH):
> sudo rsync -aive lsh -M--copy-as=joe src/ lh:dest/
something that is useful over a slow connection.
Rsync supports multiple compression methods and will choose one for you
- unless you force the choice using the `--compress-choice` option.
+ unless you force the choice using the `--compress-choice` (`--zc`) option.
- Run `rsync -V` to see the default compress list compiled into your version.
+ Run `rsync --version` to see the default compress list compiled into your
+ version.
When both sides of the transfer are at least 3.2.0, rsync chooses the first
algorithm in the client's list of choices that is also in the server's list
The default order can be customized by setting the environment variable
RSYNC_COMPRESS_LIST to a space-separated list of acceptable compression
- names. If the environment variable contains a "`&`" character, the string
- is separated into the "client list & server list" otherwise the same string
- applies to both. If the string (or string portion) contains no
+ names. If the string contains a "`&`" character, it is separated into the
+ "client string & server string", otherwise the same string applies to both.
+ If the string (or string portion) contains no
non-whitespace characters, the default compress list is used. Any unknown
compression names are discarded from the list, but a list with only invalid
names results in a failed negotiation.
specify `-zz`.
See also the `--skip-compress` option for the default list of file suffixes
- that will trasnferred with no (or minimal) compression.
+ that will be transferred with no (or minimal) compression.
0. `--compress-choice=STR`, `--zc=STR`
- `zlib`
- `none`
- Run `rsync -V` to see the default compress list compiled into your version
- (which may differ from the above list).
+ Run `rsync --version` to see the default compress list compiled into your
+ version (which may differ from the list above).
Note that if you see an error about an option named `--old-compress` or
`--new-compress`, this is rsync trying to send the `--compress-choice=zlib`
"off").
The level values vary depending on the checksum in effect. Because rsync
- will negotiate a checksum choice by default when the remote rsync is new
- enough, it can be good to combine this option with a `--compress-choice`
+ will negotiate a checksum choice by default (when the remote rsync is new
+ enough), it can be good to combine this option with a `--compress-choice`
(`--zc`) option unless you're sure of the choice in effect. For example:
> rsync -aiv --zc=zstd --zl=22 host:src/ dest/
possible. Rsync sets the compression level on a per-file basis based on
the file's suffix. If the compression algorithm has an "off" level (such
as zlib/zlibx) then no compression occurs for those files. Other
- algorithms have the level minimized to reduces the CPU usage as much as
- possible.
+ algorithms that support changing the streaming level on-the-fly will have
+ the level minimized to reduces the CPU usage as much as possible for a
+ matching file. At this time, only zlib & zlibx compression support this
+ changing of levels on a per-file basis.
The **LIST** should be one or more file suffixes (without the dot) separated
by slashes (`/`). You may specify an empty string to indicate that no files
[comment]: # (This list gets used for the default-dont-compress.h file.)
+ > 3g2
+ > 3gp
> 7z
+ > aac
> ace
> apk
> avi
> bz2
> deb
+ > dmg
+ > ear
+ > f4v
> flac
+ > flv
> gpg
> gz
> iso
> jar
> jpeg
> jpg
+ > lrz
> lz
> lz4
> lzma
> lzo
+ > m1a
+ > m1v
+ > m2a
+ > m2ts
+ > m2v
+ > m4a
+ > m4b
+ > m4p
+ > m4r
+ > m4v
+ > mka
> mkv
> mov
+ > mp1
+ > mp2
> mp3
> mp4
+ > mpa
+ > mpeg
+ > mpg
+ > mpv
+ > mts
> odb
> odf
> odg
> odp
> ods
> odt
+ > oga
> ogg
+ > ogm
> ogv
+ > ogx
> opus
> otg
> oth
> ott
> oxt
> png
+ > qt
> rar
> rpm
> rz
> rzip
+ > spx
> squashfs
> sxc
> sxd
> sxg
> sxm
> sxw
+ > sz
> tbz
+ > tbz2
> tgz
> tlz
+ > ts
> txz
> tzo
+ > vob
+ > war
> webm
> webp
> xz
option to have any effect, the `-g` (`--groups`) option must be used (or
implied), and the receiver will need to have permissions to set that group.
+ If your shell complains about the wildcards, use `--protect-args` (`-s`).
+
0. `--chown=USER:GROUP`
This option forces all files to be owned by USER with group GROUP. This is
USER is empty, a leading colon must be supplied.
If you specify "`--chown=foo:bar`", this is exactly the same as specifying
- "`--usermap=*:foo --groupmap=*:bar`", only easier.
+ "`--usermap=*:foo --groupmap=*:bar`", only easier. If your shell complains
+ about the wildcards, use `--protect-args` (`-s`).
0. `--timeout=SECONDS`
directory, an `L` for a symlink, a `D` for a device, and a `S` for a
special file (e.g. named sockets and fifos).
- The other letters in the string above are the actual letters that will be
- output if the associated attribute for the item is being updated or a "."
- for no change. Three exceptions to this are: (1) a newly created item
- replaces each letter with a "+", (2) an identical item replaces the dots
- with spaces, and (3) an unknown attribute replaces each letter with a "?"
- (this can happen when talking to an older rsync).
+ The other letters in the string indicate if some attributes of the file
+ have changed, as follows:
+
+ - "`.`" - the attribute is unchanged.
+ - "`+`" - the file is newly created.
+ - "` `" - all the attributes are unchanged (all dots turn to spaces).
+ - "`?`" - the change is unknown (when the remote rsync is old).
+ - A letter indicates an attribute is being updated.
The attribute that is associated with each letter is as follows:
value (requires `--owner` and super-user privileges).
- A `g` means the group is different and is being updated to the sender's
value (requires `--group` and the authority to set the group).
- - A `u` means the access (use) time is different and is being updated to
- the sender's value (requires `--atimes`). An alternate value of `U`
- means that the access time will be set to the transfer time, which
- happens when a symlink or directory is updated.
- - The `a` means that the ACL information changed.
- - The `x` means that the extended attribute information changed.
+ - A `u`|`n`|`b` indicates the following information: `u` means the access
+ (use) time is different and is being updated to the sender's value
+ (requires `--atimes`); `n` means the create time (newness) is different
+ and is being updated to the sender's value (requires `--crtimes`); `b`
+ means that both the access and create times are being updated.
+ - The `a` means that the ACL information is being changed.
+ - The `x` means that the extended attribute information is being changed.
One other output is possible: when deleting files, the "%i" will output the
string "`*deleting`" for each item that is being removed (assuming that you
level by one. You can take the level down to 0 (to output numbers as pure
digits) by specifying the `--no-human-readable` (`--no-h`) option.
- The unit letters that are appended in levels 2 and 3 are: K (kilo), M
- (mega), G (giga), or T (tera). For example, a 1234567-byte file would
- output as 1.23M in level-2 (assuming that a period is your local decimal
- point).
+ The unit letters that are appended in levels 2 and 3 are: `K` (kilo), `M`
+ (mega), `G` (giga), `T` (tera), or `P` (peta). For example, a 1234567-byte
+ file would output as 1.23M in level-2 (assuming that a period is your local
+ decimal point).
Backward compatibility note: versions of rsync prior to 3.1.0 do not
support human-readable level 1, and they default to level 0. Thus,
can do if you want rsync to cleanup old `.~tmp~` dirs that might be lying
around. Conflicts with `--inplace` and `--append`.
+ This option implies `--no-inc-recursive` since it needs the full file list
+ in memory in order to be able to iterate over it at the end.
+
This option uses more memory on the receiving side (one bit per file
transferred) and also requires enough free disk space on the receiving side
to hold an additional copy of all the updated files. Note also that you
fractional value (e.g. "`--bwlimit=1.5m`"). If no suffix is specified, the
value will be assumed to be in units of 1024 bytes (as if "K" or "KiB" had
been appended). See the `--max-size` option for a description of all the
- available suffixes. A value of zero specifies no limit.
+ available suffixes. A value of 0 specifies no limit.
For backward-compatibility reasons, the rate limit will be rounded to the
nearest KiB unit, so no rate smaller than 1024 bytes per second is
buffered, while other can show up as very slow when the flushing of the
output buffer occurs. This may be fixed in a future version.
+0. `--stop-after=MINS
+
+ This option tells rsync to stop copying when the specified number of
+ minutes has elapsed.
+
+ Rsync also accepts an earlier version of this option: `--time-limit=MINS`.
+
+ For maximal flexibility, rsync does not communicate this option to the
+ remote rsync since it is usually enough that one side of the connection
+ quits as specified. This allows the option's use even when only one side
+ of the connection supports it. You can tell the remote side about the time
+ limit using `--remote-option` (`-M`), should the need arise.
+
+0. `--stop-at=y-m-dTh:m
+
+ This option tells rsync to stop copying when the specified point in time
+ has been reached. The date & time can be fully specified in a numeric
+ format of year-month-dayThour:minute (e.g. 2000-12-31T23:59) in the local
+ timezone. You may choose to separate the date numbers using slashes
+ instead of dashes.
+
+ The value can also be abbreviated in a variety of ways, such as specifying
+ a 2-digit year and/or leaving off various values. In all cases, the value
+ will be taken to be the next possible point in time where the supplied
+ information matches. If the value specifies the current time or a past
+ time, rsync exits with an error.
+
+ For example, "1-30" specifies the next January 30th (at midnight local
+ time), "14:00" specifies the next 2 P.M., "1" specifies the next 1st of the
+ month at midnight, "31" specifies the next month where we can stop on its
+ 31st day, and ":59" specifies the next 59th minute after the hour.
+
+ For maximal flexibility, rsync does not communicate this option to the
+ remote rsync since it is usually enough that one side of the connection
+ quits as specified. This allows the option's use even when only one side
+ of the connection supports it. You can tell the remote side about the time
+ limit using `--remote-option` (`-M`), should the need arise. Do keep in
+ mind that the remote host may have a different default timezone than your
+ local host.
+
0. `--write-batch=FILE`
Record a file that can later be applied to another identical destination
These options also exist in the `--daemon` mode section.
If rsync was complied without support for IPv6, the `--ipv6` option will
- have no effect. The `rsync -V` output will contain "`no IPv6`" if is the
- case.
+ have no effect. The `rsync --version` output will contain "`no IPv6`" if
+ is the case.
0. `--checksum-seed=NUM`
These options also exist in the regular rsync options section.
If rsync was complied without support for IPv6, the `--ipv6` option will
- have no effect. The `rsync -V` output will contain "`no IPv6`" if is the
- case.
+ have no effect. The `rsync --version` output will contain "`no IPv6`" if
+ is the case.
0. `--help`, `-h`
git.samba.org / rsync.git / blobdiff