1 mailto(rsync-bugs@samba.org)
2 manpage(rsync)(1)(28 Jan 2018)()()
3 manpagename(rsync)(a fast, versatile, remote (and local) file-copying tool)
6 verb(Local: rsync [OPTION...] SRC... [DEST]
8 Access via remote shell:
9 Pull: rsync [OPTION...] [USER@]HOST:SRC... [DEST]
10 Push: rsync [OPTION...] SRC... [USER@]HOST:DEST
12 Access via rsync daemon:
13 Pull: rsync [OPTION...] [USER@]HOST::SRC... [DEST]
14 rsync [OPTION...] rsync://[USER@]HOST[:PORT]/SRC... [DEST]
15 Push: rsync [OPTION...] SRC... [USER@]HOST::DEST
16 rsync [OPTION...] SRC... rsync://[USER@]HOST[:PORT]/DEST)
18 Usages with just one SRC arg and no DEST arg will list the source files
23 Rsync is a fast and extraordinarily versatile file copying tool. It can
24 copy locally, to/from another host over any remote shell, or to/from a
25 remote rsync daemon. It offers a large number of options that control
26 every aspect of its behavior and permit very flexible specification of the
27 set of files to be copied. It is famous for its delta-transfer algorithm,
28 which reduces the amount of data sent over the network by sending only the
29 differences between the source files and the existing files in the
30 destination. Rsync is widely used for backups and mirroring and as an
31 improved copy command for everyday use.
33 Rsync finds files that need to be transferred using a "quick check"
34 algorithm (by default) that looks for files that have changed in size or
35 in last-modified time. Any changes in the other preserved attributes (as
36 requested by options) are made on the destination file directly when the
37 quick check indicates that the file's data does not need to be updated.
39 Some of the additional features of rsync are:
42 it() support for copying links, devices, owners, groups, and permissions
43 it() exclude and exclude-from options similar to GNU tar
44 it() a CVS exclude mode for ignoring the same files that CVS would ignore
45 it() can use any transparent remote shell, including ssh or rsh
46 it() does not require super-user privileges
47 it() pipelining of file transfers to minimize latency costs
48 it() support for anonymous or authenticated rsync daemons (ideal for
52 manpagesection(GENERAL)
54 Rsync copies files either to or from a remote host, or locally on the
55 current host (it does not support copying files between two remote hosts).
57 There are two different ways for rsync to contact a remote system: using a
58 remote-shell program as the transport (such as ssh or rsh) or contacting an
59 rsync daemon directly via TCP. The remote-shell transport is used whenever
60 the source or destination path contains a single colon (:) separator after
61 a host specification. Contacting an rsync daemon directly happens when the
62 source or destination path contains a double colon (::) separator after a
63 host specification, OR when an rsync:// URL is specified (see also the
64 "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" section for
65 an exception to this latter rule).
67 As a special case, if a single source arg is specified without a
68 destination, the files are listed in an output format similar to "ls -l".
70 As expected, if neither the source or destination path specify a remote
71 host, the copy occurs locally (see also the bf(--list-only) option).
73 Rsync refers to the local side as the "client" and the remote side as the
74 "server". Don't confuse "server" with an rsync daemon -- a daemon is always a
75 server, but a server can be either a daemon or a remote-shell spawned process.
79 See the file README for installation instructions.
81 Once installed, you can use rsync to any machine that you can access via
82 a remote shell (as well as some that you can access using the rsync
83 daemon-mode protocol). For remote transfers, a modern rsync uses ssh
84 for its communications, but it may have been configured to use a
85 different remote shell by default, such as rsh or remsh.
87 You can also specify any remote shell you like, either by using the bf(-e)
88 command line option, or by setting the RSYNC_RSH environment variable.
90 Note that rsync must be installed on both the source and destination
95 You use rsync in the same way you use rcp. You must specify a source
96 and a destination, one of which may be remote.
98 Perhaps the best way to explain the syntax is with some examples:
100 quote(tt(rsync -t *.c foo:src/))
102 This would transfer all files matching the pattern *.c from the
103 current directory to the directory src on the machine foo. If any of
104 the files already exist on the remote system then the rsync
105 remote-update protocol is used to update the file by sending only the
106 differences in the data. Note that the expansion of wildcards on the
107 commandline (*.c) into a list of files is handled by the shell before
108 it runs rsync and not by rsync itself (exactly the same as all other
109 posix-style programs).
111 quote(tt(rsync -avz foo:src/bar /data/tmp))
113 This would recursively transfer all files from the directory src/bar on the
114 machine foo into the /data/tmp/bar directory on the local machine. The
115 files are transferred in "archive" mode, which ensures that symbolic
116 links, devices, attributes, permissions, ownerships, etc. are preserved
117 in the transfer. Additionally, compression will be used to reduce the
118 size of data portions of the transfer.
120 quote(tt(rsync -avz foo:src/bar/ /data/tmp))
122 A trailing slash on the source changes this behavior to avoid creating an
123 additional directory level at the destination. You can think of a trailing
124 / on a source as meaning "copy the contents of this directory" as opposed
125 to "copy the directory by name", but in both cases the attributes of the
126 containing directory are transferred to the containing directory on the
127 destination. In other words, each of the following commands copies the
128 files in the same way, including their setting of the attributes of
132 tt(rsync -av /src/foo /dest)nl()
133 tt(rsync -av /src/foo/ /dest/foo)nl()
136 Note also that host and module references don't require a trailing slash to
137 copy the contents of the default directory. For example, both of these
138 copy the remote directory's contents into "/dest":
141 tt(rsync -av host: /dest)nl()
142 tt(rsync -av host::module /dest)nl()
145 You can also use rsync in local-only mode, where both the source and
146 destination don't have a ':' in the name. In this case it behaves like
147 an improved copy command.
149 Finally, you can list all the (listable) modules available from a
150 particular rsync daemon by leaving off the module name:
152 quote(tt(rsync somehost.mydomain.com::))
154 See the following section for more details.
156 manpagesection(ADVANCED USAGE)
158 The syntax for requesting multiple files from a remote host is done by
159 specifying additional remote-host args in the same style as the first,
160 or with the hostname omitted. For instance, all these work:
162 quote(tt(rsync -av host:file1 :file2 host:file{3,4} /dest/)nl()
163 tt(rsync -av host::modname/file{1,2} host::modname/file3 /dest/)nl()
164 tt(rsync -av host::modname/file1 ::modname/file{3,4}))
166 Older versions of rsync required using quoted spaces in the SRC, like these
169 quote(tt(rsync -av host:'dir1/file1 dir2/file2' /dest)nl()
170 tt(rsync host::'modname/dir1/file1 modname/dir2/file2' /dest))
172 This word-splitting still works (by default) in the latest rsync, but is
173 not as easy to use as the first method.
175 If you need to transfer a filename that contains whitespace, you can either
176 specify the bf(--protect-args) (bf(-s)) option, or you'll need to escape
177 the whitespace in a way that the remote shell will understand. For
180 quote(tt(rsync -av host:'file\ name\ with\ spaces' /dest))
182 manpagesection(CONNECTING TO AN RSYNC DAEMON)
184 It is also possible to use rsync without a remote shell as the transport.
185 In this case you will directly connect to a remote rsync daemon, typically
186 using TCP port 873. (This obviously requires the daemon to be running on
187 the remote system, so refer to the STARTING AN RSYNC DAEMON TO ACCEPT
188 CONNECTIONS section below for information on that.)
190 Using rsync in this way is the same as using it with a remote shell except
194 it() you either use a double colon :: instead of a single colon to
195 separate the hostname from the path, or you use an rsync:// URL.
196 it() the first word of the "path" is actually a module name.
197 it() the remote daemon may print a message of the day when you
199 it() if you specify no path name on the remote daemon then the
200 list of accessible paths on the daemon will be shown.
201 it() if you specify no local destination then a listing of the
202 specified files on the remote daemon is provided.
203 it() you must not specify the bf(--rsh) (bf(-e)) option (since
204 that overrides the daemon connection to use ssh -- see USING
205 RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION below).
208 An example that copies all the files in a remote module named "src":
210 verb( rsync -av host::src /dest)
212 Some modules on the remote daemon may require authentication. If so,
213 you will receive a password prompt when you connect. You can avoid the
214 password prompt by setting the environment variable RSYNC_PASSWORD to
215 the password you want to use or using the bf(--password-file) option. This
216 may be useful when scripting rsync.
218 WARNING: On some systems environment variables are visible to all
219 users. On those systems using bf(--password-file) is recommended.
221 You may establish the connection via a web proxy by setting the
222 environment variable RSYNC_PROXY to a hostname:port pair pointing to
223 your web proxy. Note that your web proxy's configuration must support
224 proxy connections to port 873.
226 You may also establish a daemon connection using a program as a proxy by
227 setting the environment variable RSYNC_CONNECT_PROG to the commands you
228 wish to run in place of making a direct socket connection. The string may
229 contain the escape "%H" to represent the hostname specified in the rsync
230 command (so use "%%" if you need a single "%" in your string). For
233 verb( export RSYNC_CONNECT_PROG='ssh proxyhost nc %H 873'
234 rsync -av targethost1::module/src/ /dest/
235 rsync -av rsync://targethost2/module/src/ /dest/ )
237 The command specified above uses ssh to run nc (netcat) on a proxyhost,
238 which forwards all data to port 873 (the rsync daemon) on the targethost
241 Note also that if the RSYNC_SHELL environment variable is set, that
242 program will be used to run the RSYNC_CONNECT_PROG command instead of
243 using the default shell of the code(system()) call.
245 manpagesection(USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION)
247 It is sometimes useful to use various features of an rsync daemon (such as
248 named modules) without actually allowing any new socket connections into a
249 system (other than what is already required to allow remote-shell access).
250 Rsync supports connecting to a host using a remote shell and then spawning
251 a single-use "daemon" server that expects to read its config file in the
252 home dir of the remote user. This can be useful if you want to encrypt a
253 daemon-style transfer's data, but since the daemon is started up fresh by
254 the remote user, you may not be able to use features such as chroot or
255 change the uid used by the daemon. (For another way to encrypt a daemon
256 transfer, consider using ssh to tunnel a local port to a remote machine and
257 configure a normal rsync daemon on that remote host to only allow
258 connections from "localhost".)
260 From the user's perspective, a daemon transfer via a remote-shell
261 connection uses nearly the same command-line syntax as a normal
262 rsync-daemon transfer, with the only exception being that you must
263 explicitly set the remote shell program on the command-line with the
264 bf(--rsh=COMMAND) option. (Setting the RSYNC_RSH in the environment
265 will not turn on this functionality.) For example:
267 verb( rsync -av --rsh=ssh host::module /dest)
269 If you need to specify a different remote-shell user, keep in mind that the
270 user@ prefix in front of the host is specifying the rsync-user value (for a
271 module that requires user-based authentication). This means that you must
272 give the '-l user' option to ssh when specifying the remote-shell, as in
273 this example that uses the short version of the bf(--rsh) option:
275 verb( rsync -av -e "ssh -l ssh-user" rsync-user@host::module /dest)
277 The "ssh-user" will be used at the ssh level; the "rsync-user" will be
278 used to log-in to the "module".
280 manpagesection(STARTING AN RSYNC DAEMON TO ACCEPT CONNECTIONS)
282 In order to connect to an rsync daemon, the remote system needs to have a
283 daemon already running (or it needs to have configured something like inetd
284 to spawn an rsync daemon for incoming connections on a particular port).
285 For full information on how to start a daemon that will handling incoming
286 socket connections, see the bf(rsyncd.conf)(5) man page -- that is the config
287 file for the daemon, and it contains the full details for how to run the
288 daemon (including stand-alone and inetd configurations).
290 If you're using one of the remote-shell transports for the transfer, there is
291 no need to manually start an rsync daemon.
293 manpagesection(SORTED TRANSFER ORDER)
295 Rsync always sorts the specified filenames into its internal transfer list.
296 This handles the merging together of the contents of identically named
297 directories, makes it easy to remove duplicate filenames, and may confuse
298 someone when the files are transferred in a different order than what was
299 given on the command-line.
301 If you need a particular file to be transferred prior to another, either
302 separate the files into different rsync calls, or consider using
303 bf(--delay-updates) (which doesn't affect the sorted transfer order, but
304 does make the final file-updating phase happen much more rapidly).
306 manpagesection(EXAMPLES)
308 Here are some examples of how I use rsync.
310 To backup my wife's home directory, which consists of large MS Word
311 files and mail folders, I use a cron job that runs
313 quote(tt(rsync -Cavz . arvidsjaur:backup))
315 each night over a PPP connection to a duplicate directory on my machine
318 To synchronize my samba source trees I use the following Makefile
322 rsync -avuzb --exclude '*~' samba:samba/ .
324 rsync -Cavuzb . samba:samba/
327 this allows me to sync with a CVS directory at the other end of the
328 connection. I then do CVS operations on the remote machine, which saves a
329 lot of time as the remote CVS protocol isn't very efficient.
331 I mirror a directory between my "old" and "new" ftp sites with the
334 tt(rsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge")
336 This is launched from cron every few hours.
338 manpagesection(OPTIONS SUMMARY)
340 Here is a short summary of the options available in rsync. Please refer
341 to the detailed description below for a complete description. verb(
342 -v, --verbose increase verbosity
343 --info=FLAGS fine-grained informational verbosity
344 --debug=FLAGS fine-grained debug verbosity
345 --msgs2stderr special output handling for debugging
346 -q, --quiet suppress non-error messages
347 --no-motd suppress daemon-mode MOTD (see caveat)
348 -c, --checksum skip based on checksum, not mod-time & size
349 -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X)
350 --no-OPTION turn off an implied OPTION (e.g. --no-D)
351 -r, --recursive recurse into directories
352 -R, --relative use relative path names
353 --no-implied-dirs don't send implied dirs with --relative
354 -b, --backup make backups (see --suffix & --backup-dir)
355 --backup-dir=DIR make backups into hierarchy based in DIR
356 --suffix=SUFFIX backup suffix (default ~ w/o --backup-dir)
357 -u, --update skip files that are newer on the receiver
358 --inplace update destination files in-place
359 --append append data onto shorter files
360 --append-verify --append w/old data in file checksum
361 -d, --dirs transfer directories without recursing
362 -l, --links copy symlinks as symlinks
363 -L, --copy-links transform symlink into referent file/dir
364 --copy-unsafe-links only "unsafe" symlinks are transformed
365 --safe-links ignore symlinks that point outside the tree
366 --munge-links munge symlinks to make them safer
367 -k, --copy-dirlinks transform symlink to dir into referent dir
368 -K, --keep-dirlinks treat symlinked dir on receiver as dir
369 -H, --hard-links preserve hard links
370 -p, --perms preserve permissions
371 -E, --executability preserve executability
372 --chmod=CHMOD affect file and/or directory permissions
373 -A, --acls preserve ACLs (implies -p)
374 -X, --xattrs preserve extended attributes
375 -o, --owner preserve owner (super-user only)
376 -g, --group preserve group
377 --devices preserve device files (super-user only)
378 --specials preserve special files
379 -D same as --devices --specials
380 -t, --times preserve modification times
381 -U, --atimes preserve access (use) times
382 --open-noatime avoid changing the atime on opened files
383 -O, --omit-dir-times omit directories from --times
384 -J, --omit-link-times omit symlinks from --times
385 --super receiver attempts super-user activities
386 --fake-super store/recover privileged attrs using xattrs
387 -S, --sparse turn sequences of nulls into sparse blocks
388 --preallocate allocate dest files before writing
389 --write-devices write to devices as files (implies --inplace)
390 -n, --dry-run perform a trial run with no changes made
391 -W, --whole-file copy files whole (w/o delta-xfer algorithm)
392 --checksum-choice=STR choose the checksum algorithms
393 -x, --one-file-system don't cross filesystem boundaries
394 -B, --block-size=SIZE force a fixed checksum block-size
395 -e, --rsh=COMMAND specify the remote shell to use
396 --rsync-path=PROGRAM specify the rsync to run on remote machine
397 --existing skip creating new files on receiver
398 --ignore-existing skip updating files that exist on receiver
399 --remove-source-files sender removes synchronized files (non-dir)
400 --del an alias for --delete-during
401 --delete delete extraneous files from dest dirs
402 --delete-before receiver deletes before xfer, not during
403 --delete-during receiver deletes during the transfer
404 --delete-delay find deletions during, delete after
405 --delete-after receiver deletes after transfer, not during
406 --delete-excluded also delete excluded files from dest dirs
407 --ignore-missing-args ignore missing source args without error
408 --delete-missing-args delete missing source args from destination
409 --ignore-errors delete even if there are I/O errors
410 --force force deletion of dirs even if not empty
411 --max-delete=NUM don't delete more than NUM files
412 --max-size=SIZE don't transfer any file larger than SIZE
413 --min-size=SIZE don't transfer any file smaller than SIZE
414 --partial keep partially transferred files
415 --partial-dir=DIR put a partially transferred file into DIR
416 --delay-updates put all updated files into place at end
417 -m, --prune-empty-dirs prune empty directory chains from file-list
418 --numeric-ids don't map uid/gid values by user/group name
419 --usermap=STRING custom username mapping
420 --groupmap=STRING custom groupname mapping
421 --chown=USER:GROUP simple username/groupname mapping
422 --timeout=SECONDS set I/O timeout in seconds
423 --contimeout=SECONDS set daemon connection timeout in seconds
424 -I, --ignore-times don't skip files that match size and time
425 --size-only skip files that match in size
426 -@, --modify-window=NUM set the accuracy for mod-time comparisons
427 -T, --temp-dir=DIR create temporary files in directory DIR
428 -y, --fuzzy find similar file for basis if no dest file
429 --compare-dest=DIR also compare received files relative to DIR
430 --copy-dest=DIR ... and include copies of unchanged files
431 --link-dest=DIR hardlink to files in DIR when unchanged
432 -z, --compress compress file data during the transfer
433 --compress-level=NUM explicitly set compression level
434 --skip-compress=LIST skip compressing files with suffix in LIST
435 -C, --cvs-exclude auto-ignore files in the same way CVS does
436 -f, --filter=RULE add a file-filtering RULE
437 -F same as --filter='dir-merge /.rsync-filter'
438 repeated: --filter='- .rsync-filter'
439 --exclude=PATTERN exclude files matching PATTERN
440 --exclude-from=FILE read exclude patterns from FILE
441 --include=PATTERN don't exclude files matching PATTERN
442 --include-from=FILE read include patterns from FILE
443 --files-from=FILE read list of source-file names from FILE
444 -0, --from0 all *from/filter files are delimited by 0s
445 -s, --protect-args no space-splitting; wildcard chars only
446 --copy-as=USER[:GROUP] specify user & optional group for the copy
447 --address=ADDRESS bind address for outgoing socket to daemon
448 --port=PORT specify double-colon alternate port number
449 --sockopts=OPTIONS specify custom TCP options
450 --blocking-io use blocking I/O for the remote shell
451 --outbuf=N|L|B set out buffering to None, Line, or Block
452 --stats give some file-transfer stats
453 -8, --8-bit-output leave high-bit chars unescaped in output
454 -h, --human-readable output numbers in a human-readable format
455 --progress show progress during transfer
456 -P same as --partial --progress
457 -i, --itemize-changes output a change-summary for all updates
458 -M, --remote-option=OPTION send OPTION to the remote side only
459 --out-format=FORMAT output updates using the specified FORMAT
460 --log-file=FILE log what we're doing to the specified FILE
461 --log-file-format=FMT log updates using the specified FMT
462 --password-file=FILE read daemon-access password from FILE
463 --list-only list the files instead of copying them
464 --bwlimit=RATE limit socket I/O bandwidth
465 --write-batch=FILE write a batched update to FILE
466 --only-write-batch=FILE like --write-batch but w/o updating dest
467 --read-batch=FILE read a batched update from FILE
468 --protocol=NUM force an older protocol version to be used
469 --iconv=CONVERT_SPEC request charset conversion of filenames
470 --checksum-seed=NUM set block/file checksum seed (advanced)
471 -4, --ipv4 prefer IPv4
472 -6, --ipv6 prefer IPv6
473 --version print version number
474 (-h) --help show this help (see below for -h comment))
476 Rsync can also be run as a daemon, in which case the following options are
478 --daemon run as an rsync daemon
479 --address=ADDRESS bind to the specified address
480 --bwlimit=RATE limit socket I/O bandwidth
481 --config=FILE specify alternate rsyncd.conf file
482 -M, --dparam=OVERRIDE override global daemon config parameter
483 --no-detach do not detach from the parent
484 --port=PORT listen on alternate port number
485 --log-file=FILE override the "log file" setting
486 --log-file-format=FMT override the "log format" setting
487 --sockopts=OPTIONS specify custom TCP options
488 -v, --verbose increase verbosity
489 -4, --ipv4 prefer IPv4
490 -6, --ipv6 prefer IPv6
491 -h, --help show this help (if used after --daemon))
495 Rsync accepts both long (double-dash + word) and short (single-dash + letter)
496 options. The full list of the available options are described below. If an
497 option can be specified in more than one way, the choices are comma-separated.
498 Some options only have a long variant, not a short. If the option takes a
499 parameter, the parameter is only listed after the long variant, even though it
500 must also be specified for the short. When specifying a parameter, you can
501 either use the form --option=param or replace the '=' with whitespace. The
502 parameter may need to be quoted in some manner for it to survive the shell's
503 command-line parsing. Keep in mind that a leading tilde (~) in a filename is
504 substituted by your shell, so --option=~/foo will not change the tilde into
505 your home directory (remove the '=' for that).
509 dit(bf(--help)) Print a short help page describing the options
510 available in rsync and exit. For backward-compatibility with older
511 versions of rsync, the help will also be output if you use the bf(-h)
512 option without any other args.
514 dit(bf(--version)) print the rsync version number and exit.
516 dit(bf(-v, --verbose)) This option increases the amount of information you
517 are given during the transfer. By default, rsync works silently. A
518 single bf(-v) will give you information about what files are being
519 transferred and a brief summary at the end. Two bf(-v) options will give you
520 information on what files are being skipped and slightly more
521 information at the end. More than two bf(-v) options should only be used if
522 you are debugging rsync.
524 In a modern rsync, the bf(-v) option is equivalent to the setting of groups
525 of bf(--info) and bf(--debug) options. You can choose to use these newer
526 options in addition to, or in place of using bf(--verbose), as any
527 fine-grained settings override the implied settings of bf(-v). Both
528 bf(--info) and bf(--debug) have a way to ask for help that tells you
529 exactly what flags are set for each increase in verbosity.
531 However, do keep in mind that a daemon's "max verbosity" setting will limit how
532 high of a level the various individual flags can be set on the daemon side.
533 For instance, if the max is 2, then any info and/or debug flag that is set to
534 a higher value than what would be set by bf(-vv) will be downgraded to the
535 bf(-vv) level in the daemon's logging.
537 dit(bf(--info=FLAGS))
538 This option lets you have fine-grained control over the
540 output you want to see. An individual flag name may be followed by a level
541 number, with 0 meaning to silence that output, 1 being the default output
542 level, and higher numbers increasing the output of that flag (for those
543 that support higher levels). Use
545 to see all the available flag names, what they output, and what flag names
546 are added for each increase in the verbose level. Some examples:
548 verb( rsync -a --info=progress2 src/ dest/
549 rsync -avv --info=stats2,misc1,flist0 src/ dest/ )
551 Note that bf(--info=name)'s output is affected by the bf(--out-format) and
552 bf(--itemize-changes) (bf(-i)) options. See those options for more
553 information on what is output and when.
555 This option was added to 3.1.0, so an older rsync on the server side might
556 reject your attempts at fine-grained control (if one or more flags needed
557 to be send to the server and the server was too old to understand them).
558 See also the "max verbosity" caveat above when dealing with a daemon.
560 dit(bf(--debug=FLAGS))
561 This option lets you have fine-grained control over the debug
562 output you want to see. An individual flag name may be followed by a level
563 number, with 0 meaning to silence that output, 1 being the default output
564 level, and higher numbers increasing the output of that flag (for those
565 that support higher levels). Use
567 to see all the available flag names, what they output, and what flag names
568 are added for each increase in the verbose level. Some examples:
570 verb( rsync -avvv --debug=none src/ dest/
571 rsync -avA --del --debug=del2,acl src/ dest/ )
573 Note that some debug messages will only be output when bf(--msgs2stderr) is
574 specified, especially those pertaining to I/O and buffer debugging.
576 This option was added to 3.1.0, so an older rsync on the server side might
577 reject your attempts at fine-grained control (if one or more flags needed
578 to be send to the server and the server was too old to understand them).
579 See also the "max verbosity" caveat above when dealing with a daemon.
581 dit(bf(--msgs2stderr)) This option changes rsync to send all its output
582 directly to stderr rather than to send messages to the client side via the
583 protocol (which normally outputs info messages via stdout). This is mainly
584 intended for debugging in order to avoid changing the data sent via the
585 protocol, since the extra protocol data can change what is being tested.
586 The option does not affect the remote side of a transfer without using
587 bf(--remote-option) -- e.g. bf(-M--msgs2stderr).
588 Also keep in mind that a daemon connection does not have a stderr channel to send
589 messages back to the client side, so if you are doing any daemon-transfer
590 debugging using this option, you should start up a daemon using bf(--no-detach)
591 so that you can see the stderr output on the daemon side.
593 This option has the side-effect of making stderr output get line-buffered so
594 that the merging of the output of 3 programs happens in a more readable manner.
596 dit(bf(-q, --quiet)) This option decreases the amount of information you
597 are given during the transfer, notably suppressing information messages
598 from the remote server. This option is useful when invoking rsync from
601 dit(bf(--no-motd)) This option affects the information that is output
602 by the client at the start of a daemon transfer. This suppresses the
603 message-of-the-day (MOTD) text, but it also affects the list of modules
604 that the daemon sends in response to the "rsync host::" request (due to
605 a limitation in the rsync protocol), so omit this option if you want to
606 request the list of modules from the daemon.
608 dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
609 already the same size and have the same modification timestamp.
610 This option turns off this "quick check" behavior, causing all files to
613 dit(bf(--size-only)) This modifies rsync's "quick check" algorithm for
614 finding files that need to be transferred, changing it from the default of
615 transferring files with either a changed size or a changed last-modified
616 time to just looking for files that have changed in size. This is useful
617 when starting to use rsync after using another mirroring system which may
618 not preserve timestamps exactly.
620 dit(bf(-@, --modify-window)) When comparing two timestamps, rsync treats the
621 timestamps as being equal if they differ by no more than the modify-window
622 value. The default is 0, which matches just integer seconds. If you specify a
623 negative value (and the receiver is at least version 3.1.3) then nanoseconds
624 will also be taken into account. Specifying 1 is useful for copies to/from MS
625 Windows FAT filesystems, because FAT represents times with a 2-second
626 resolution (allowing times to differ from the original by up to 1 second).
628 If you want all your transfers to default to comparing nanoseconds, you can
629 create a ~/.popt file and put these lines in it:
631 verb( rsync alias -a -a@-1)
632 verb( rsync alias -t -t@-1)
634 With that as the default, you'd need to specify bf(--modify-window=0) (aka
635 bf(-@0)) to override it and ignore nanoseconds, e.g. if you're copying between
636 ext3 and ext4, or if the receiving rsync is older than 3.1.3.
638 dit(bf(-c, --checksum)) This changes the way rsync checks if the files have
639 been changed and are in need of a transfer. Without this option, rsync
640 uses a "quick check" that (by default) checks if each file's size and time
641 of last modification match between the sender and receiver. This option
642 changes this to compare a 128-bit checksum for each file that has a
643 matching size. Generating the checksums means that both sides will expend
644 a lot of disk I/O reading all the data in the files in the transfer (and
645 this is prior to any reading that will be done to transfer changed files),
646 so this can slow things down significantly.
648 The sending side generates its checksums while it is doing the file-system
649 scan that builds the list of the available files. The receiver generates
650 its checksums when it is scanning for changed files, and will checksum any
651 file that has the same size as the corresponding sender's file: files with
652 either a changed size or a changed checksum are selected for transfer.
654 Note that rsync always verifies that each em(transferred) file was
655 correctly reconstructed on the receiving side by checking a whole-file
656 checksum that is generated as the file is transferred, but that
657 automatic after-the-transfer verification has nothing to do with this
658 option's before-the-transfer "Does this file need to be updated?" check.
660 The checksum used is auto-negotiated between the client and the server, but
661 can be overridden using either the bf(--checksum-choice) option or an
662 environment variable that is discussed in that option's section.
664 dit(bf(-a, --archive)) This is equivalent to bf(-rlptgoD). It is a quick
665 way of saying you want recursion and want to preserve almost
666 everything (with -H being a notable omission).
667 The only exception to the above equivalence is when bf(--files-from) is
668 specified, in which case bf(-r) is not implied.
670 Note that bf(-a) bf(does not preserve hardlinks), because
671 finding multiply-linked files is expensive. You must separately
674 dit(--no-OPTION) You may turn off one or more implied options by prefixing
675 the option name with "no-". Not all options may be prefixed with a "no-":
676 only options that are implied by other options (e.g. bf(--no-D),
677 bf(--no-perms)) or have different defaults in various circumstances
678 (e.g. bf(--no-whole-file), bf(--no-blocking-io), bf(--no-dirs)). You may
679 specify either the short or the long option name after the "no-" prefix
680 (e.g. bf(--no-R) is the same as bf(--no-relative)).
682 For example: if you want to use bf(-a) (bf(--archive)) but don't want
683 bf(-o) (bf(--owner)), instead of converting bf(-a) into bf(-rlptgD), you
684 could specify bf(-a --no-o) (or bf(-a --no-owner)).
686 The order of the options is important: if you specify bf(--no-r -a), the
687 bf(-r) option would end up being turned on, the opposite of bf(-a --no-r).
688 Note also that the side-effects of the bf(--files-from) option are NOT
689 positional, as it affects the default state of several options and slightly
690 changes the meaning of bf(-a) (see the bf(--files-from) option for more
693 dit(bf(-r, --recursive)) This tells rsync to copy directories
694 recursively. See also bf(--dirs) (bf(-d)).
696 Beginning with rsync 3.0.0, the recursive algorithm used is now an
697 incremental scan that uses much less memory than before and begins the
698 transfer after the scanning of the first few directories have been
699 completed. This incremental scan only affects our recursion algorithm, and
700 does not change a non-recursive transfer. It is also only possible when
701 both ends of the transfer are at least version 3.0.0.
703 Some options require rsync to know the full file list, so these options
704 disable the incremental recursion mode. These include: bf(--delete-before),
705 bf(--delete-after), bf(--prune-empty-dirs), and bf(--delay-updates).
706 Because of this, the default delete mode when you specify bf(--delete) is now
707 bf(--delete-during) when both ends of the connection are at least 3.0.0
708 (use bf(--del) or bf(--delete-during) to request this improved deletion mode
709 explicitly). See also the bf(--delete-delay) option that is a better choice
710 than using bf(--delete-after).
712 Incremental recursion can be disabled using the bf(--no-inc-recursive)
713 option or its shorter bf(--no-i-r) alias.
715 dit(bf(-R, --relative)) Use relative paths. This means that the full path
716 names specified on the command line are sent to the server rather than
717 just the last parts of the filenames. This is particularly useful when
718 you want to send several different directories at the same time. For
719 example, if you used this command:
721 verb( rsync -av /foo/bar/baz.c remote:/tmp/)
723 ... this would create a file named baz.c in /tmp/ on the remote
724 machine. If instead you used
726 verb( rsync -avR /foo/bar/baz.c remote:/tmp/)
728 then a file named /tmp/foo/bar/baz.c would be created on the remote
729 machine, preserving its full path. These extra path elements are called
730 "implied directories" (i.e. the "foo" and the "foo/bar" directories in the
733 Beginning with rsync 3.0.0, rsync always sends these implied directories as
734 real directories in the file list, even if a path element is really a
735 symlink on the sending side. This prevents some really unexpected
736 behaviors when copying the full path of a file that you didn't realize had
737 a symlink in its path. If you want to duplicate a server-side symlink,
738 include both the symlink via its path, and referent directory via its real
739 path. If you're dealing with an older rsync on the sending side, you may
740 need to use the bf(--no-implied-dirs) option.
742 It is also possible to limit the amount of path information that is sent as
743 implied directories for each path you specify. With a modern rsync on the
744 sending side (beginning with 2.6.7), you can insert a dot and a slash into
745 the source path, like this:
747 verb( rsync -avR /foo/./bar/baz.c remote:/tmp/)
749 That would create /tmp/bar/baz.c on the remote machine. (Note that the
750 dot must be followed by a slash, so "/foo/." would not be abbreviated.)
751 For older rsync versions, you would need to use a chdir to limit the
752 source path. For example, when pushing files:
754 verb( (cd /foo; rsync -avR bar/baz.c remote:/tmp/) )
756 (Note that the parens put the two commands into a sub-shell, so that the
757 "cd" command doesn't remain in effect for future commands.)
758 If you're pulling files from an older rsync, use this idiom (but only
759 for a non-daemon transfer):
761 verb( rsync -avR --rsync-path="cd /foo; rsync" \ )
762 verb( remote:bar/baz.c /tmp/)
764 dit(bf(--no-implied-dirs)) This option affects the default behavior of the
765 bf(--relative) option. When it is specified, the attributes of the implied
766 directories from the source names are not included in the transfer. This
767 means that the corresponding path elements on the destination system are
768 left unchanged if they exist, and any missing implied directories are
769 created with default attributes. This even allows these implied path
770 elements to have big differences, such as being a symlink to a directory on
773 For instance, if a command-line arg or a files-from entry told rsync to
774 transfer the file "path/foo/file", the directories "path" and "path/foo"
775 are implied when bf(--relative) is used. If "path/foo" is a symlink to
776 "bar" on the destination system, the receiving rsync would ordinarily
777 delete "path/foo", recreate it as a directory, and receive the file into
778 the new directory. With bf(--no-implied-dirs), the receiving rsync updates
779 "path/foo/file" using the existing path elements, which means that the file
780 ends up being created in "path/bar". Another way to accomplish this link
781 preservation is to use the bf(--keep-dirlinks) option (which will also
782 affect symlinks to directories in the rest of the transfer).
784 When pulling files from an rsync older than 3.0.0, you may need to use this
785 option if the sending side has a symlink in the path you request and you
786 wish the implied directories to be transferred as normal directories.
788 dit(bf(-b, --backup)) With this option, preexisting destination files are
789 renamed as each file is transferred or deleted. You can control where the
790 backup file goes and what (if any) suffix gets appended using the
791 bf(--backup-dir) and bf(--suffix) options.
793 Note that if you don't specify bf(--backup-dir), (1) the
794 bf(--omit-dir-times) option will be forced on, and (2) if bf(--delete) is
795 also in effect (without bf(--delete-excluded)), rsync will add a "protect"
796 filter-rule for the backup suffix to the end of all your existing excludes
797 (e.g. bf(-f "P *~")). This will prevent previously backed-up files from being
798 deleted. Note that if you are supplying your own filter rules, you may
799 need to manually insert your own exclude/protect rule somewhere higher up
800 in the list so that it has a high enough priority to be effective (e.g., if
801 your rules specify a trailing inclusion/exclusion of '*', the auto-added
802 rule would never be reached).
804 dit(bf(--backup-dir=DIR)) In combination with the bf(--backup) option, this
805 tells rsync to store all backups in the specified directory on the receiving
806 side. This can be used for incremental backups. You can additionally
807 specify a backup suffix using the bf(--suffix) option
808 (otherwise the files backed up in the specified directory
809 will keep their original filenames).
811 Note that if you specify a relative path, the backup directory will be
812 relative to the destination directory, so you probably want to specify
813 either an absolute path or a path that starts with "../". If an rsync
814 daemon is the receiver, the backup dir cannot go outside the module's path
815 hierarchy, so take extra care not to delete it or copy into it.
817 dit(bf(--suffix=SUFFIX)) This option allows you to override the default
818 backup suffix used with the bf(--backup) (bf(-b)) option. The default suffix is a ~
819 if no -bf(-backup-dir) was specified, otherwise it is an empty string.
821 dit(bf(-u, --update)) This forces rsync to skip any files which exist on
822 the destination and have a modified time that is newer than the source
823 file. (If an existing destination file has a modification time equal to the
824 source file's, it will be updated if the sizes are different.)
826 Note that this does not affect the copying of dirs, symlinks, or other special
827 files. Also, a difference of file format between the sender and receiver
828 is always considered to be important enough for an update, no matter what
829 date is on the objects. In other words, if the source has a directory
830 where the destination has a file, the transfer would occur regardless of
833 This option is a transfer rule, not an exclude, so it doesn't affect the
834 data that goes into the file-lists, and thus it doesn't affect deletions.
835 It just limits the files that the receiver requests to be transferred.
837 dit(bf(--inplace)) This option changes how rsync transfers a file when
838 its data needs to be updated: instead of the default method of creating
839 a new copy of the file and moving it into place when it is complete, rsync
840 instead writes the updated data directly to the destination file.
842 This has several effects:
845 it() Hard links are not broken. This means the new data will be visible
846 through other hard links to the destination file. Moreover, attempts to
847 copy differing source files onto a multiply-linked destination file will
848 result in a "tug of war" with the destination data changing back and forth.
849 it() In-use binaries cannot be updated (either the OS will prevent this from
850 happening, or binaries that attempt to swap-in their data will misbehave or
852 it() The file's data will be in an inconsistent state during the transfer
853 and will be left that way if the transfer is interrupted or if an update
855 it() A file that rsync cannot write to cannot be updated. While a super user
856 can update any file, a normal user needs to be granted write permission for
857 the open of the file for writing to be successful.
858 it() The efficiency of rsync's delta-transfer algorithm may be reduced if
859 some data in the destination file is overwritten before it can be copied to
860 a position later in the file. This does not apply if you use bf(--backup),
861 since rsync is smart enough to use the backup file as the basis file for the
865 WARNING: you should not use this option to update files that are being
866 accessed by others, so be careful when choosing to use this for a copy.
868 This option is useful for transferring large files with block-based changes
869 or appended data, and also on systems that are disk bound, not network
870 bound. It can also help keep a copy-on-write filesystem snapshot from
871 diverging the entire contents of a file that only has minor changes.
873 The option implies bf(--partial) (since an interrupted transfer does not delete
874 the file), but conflicts with bf(--partial-dir) and bf(--delay-updates).
875 Prior to rsync 2.6.4 bf(--inplace) was also incompatible with bf(--compare-dest)
878 dit(bf(--append)) This causes rsync to update a file by appending data onto
879 the end of the file, which presumes that the data that already exists on
880 the receiving side is identical with the start of the file on the sending
881 side. If a file needs to be transferred and its size on the receiver is
882 the same or longer than the size on the sender, the file is skipped. This
883 does not interfere with the updating of a file's non-content attributes
884 (e.g. permissions, ownership, etc.) when the file does not need to be
885 transferred, nor does it affect the updating of any non-regular files.
886 Implies bf(--inplace).
888 The use of bf(--append) can be dangerous if you aren't 100% sure that the files
889 that are longer have only grown by the appending of data onto the end. You
890 should thus use include/exclude/filter rules to ensure that such a transfer is
891 only affecting files that you know to be growing via appended data.
893 dit(bf(--append-verify)) This works just like the bf(--append) option, but
894 the existing data on the receiving side is included in the full-file
895 checksum verification step, which will cause a file to be resent if the
896 final verification step fails (rsync uses a normal, non-appending
897 bf(--inplace) transfer for the resend). It otherwise has the exact same
898 caveats for files that have not grown larger, so don't use this for a
901 Note: prior to rsync 3.0.0, the bf(--append) option worked like
902 bf(--append-verify), so if you are interacting with an older rsync (or the
903 transfer is using a protocol prior to 30), specifying either append option
904 will initiate an bf(--append-verify) transfer.
906 dit(bf(-d, --dirs)) Tell the sending side to include any directories that
907 are encountered. Unlike bf(--recursive), a directory's contents are not copied
908 unless the directory name specified is "." or ends with a trailing slash
909 (e.g. ".", "dir/.", "dir/", etc.). Without this option or the
910 bf(--recursive) option, rsync will skip all directories it encounters (and
911 output a message to that effect for each one). If you specify both
912 bf(--dirs) and bf(--recursive), bf(--recursive) takes precedence.
914 The bf(--dirs) option is implied by the bf(--files-from) option
915 or the bf(--list-only) option (including an implied
916 bf(--list-only) usage) if bf(--recursive) wasn't specified (so that
917 directories are seen in the listing). Specify bf(--no-dirs) (or bf(--no-d))
918 if you want to turn this off.
920 There is also a backward-compatibility helper option, bf(--old-dirs) (or
921 bf(--old-d)) that tells rsync to use a hack of "-r --exclude='/*/*'" to get
922 an older rsync to list a single directory without recursing.
927 dit(bf(-l, --links)) When symlinks are encountered, recreate the
928 symlink on the destination.
930 dit(bf(-L, --copy-links)) When symlinks are encountered, the item that
931 they point to (the referent) is copied, rather than the symlink. In older
932 versions of rsync, this option also had the side-effect of telling the
933 receiving side to follow symlinks, such as symlinks to directories. In a
934 modern rsync such as this one, you'll need to specify bf(--keep-dirlinks) (bf(-K))
935 to get this extra behavior. The only exception is when sending files to
936 an rsync that is too old to understand bf(-K) -- in that case, the bf(-L) option
937 will still have the side-effect of bf(-K) on that older receiving rsync.
939 dit(bf(--copy-unsafe-links)) This tells rsync to copy the referent of
940 symbolic links that point outside the copied tree. Absolute symlinks
941 are also treated like ordinary files, and so are any symlinks in the
942 source path itself when bf(--relative) is used. This option has no
943 additional effect if bf(--copy-links) was also specified.
945 Note that the cut-off point is the top of the transfer, which is the part of
946 the path that rsync isn't mentioning in the verbose output. If you copy
947 "/src/subdir" to "/dest/" then the "subdir" directory is a name inside the
948 transfer tree, not the top of the transfer (which is /src) so it is legal for
949 created relative symlinks to refer to other names inside the /src and /dest
950 directories. If you instead copy "/src/subdir/" (with a trailing slash) to
951 "/dest/subdir" that would not allow symlinks to any files outside of "subdir".
953 dit(bf(--safe-links)) This tells rsync to ignore any symbolic links
954 which point outside the copied tree. All absolute symlinks are
955 also ignored. Using this option in conjunction with bf(--relative) may
956 give unexpected results.
958 dit(bf(--munge-links)) This option tells rsync to (1) modify all symlinks on
959 the receiving side in a way that makes them unusable but recoverable (see
960 below), or (2) to unmunge symlinks on the sending side that had been stored in
961 a munged state. This is useful if you don't quite trust the source of the data
962 to not try to slip in a symlink to a unexpected place.
964 The way rsync disables the use of symlinks is to prefix each one with the
965 string "/rsyncd-munged/". This prevents the links from being used as long as
966 that directory does not exist. When this option is enabled, rsync will refuse
967 to run if that path is a directory or a symlink to a directory.
969 The option only affects the client side of the transfer, so if you need it to
970 affect the server, specify it via bf(--remote-option). (Note that in a local
971 transfer, the client side is the sender.)
973 This option has no affect on a daemon, since the daemon configures whether it
974 wants munged symlinks via its "munge symlinks" parameter. See also the
975 "munge-symlinks" perl script in the support directory of the source code.
977 dit(bf(-k, --copy-dirlinks)) This option causes the sending side to treat
978 a symlink to a directory as though it were a real directory. This is
979 useful if you don't want symlinks to non-directories to be affected, as
980 they would be using bf(--copy-links).
982 Without this option, if the sending side has replaced a directory with a
983 symlink to a directory, the receiving side will delete anything that is in
984 the way of the new symlink, including a directory hierarchy (as long as
985 bf(--force) or bf(--delete) is in effect).
987 See also bf(--keep-dirlinks) for an analogous option for the receiving
990 bf(--copy-dirlinks) applies to all symlinks to directories in the source. If
991 you want to follow only a few specified symlinks, a trick you can use is to
992 pass them as additional source args with a trailing slash, using bf(--relative)
993 to make the paths match up right. For example:
995 quote(tt(rsync -r --relative src/./ src/./follow-me/ dest/))
997 This works because rsync calls bf(lstat)(2) on the source arg as given, and the
998 trailing slash makes bf(lstat)(2) follow the symlink, giving rise to a directory
999 in the file-list which overrides the symlink found during the scan of "src/./".
1004 dit(bf(-K, --keep-dirlinks)) This option causes the receiving side to treat
1005 a symlink to a directory as though it were a real directory, but only if it
1006 matches a real directory from the sender. Without this option, the
1007 receiver's symlink would be deleted and replaced with a real directory.
1009 For example, suppose you transfer a directory "foo" that contains a file
1010 "file", but "foo" is a symlink to directory "bar" on the receiver. Without
1011 bf(--keep-dirlinks), the receiver deletes symlink "foo", recreates it as a
1012 directory, and receives the file into the new directory. With
1013 bf(--keep-dirlinks), the receiver keeps the symlink and "file" ends up in
1016 One note of caution: if you use bf(--keep-dirlinks), you must trust all
1017 the symlinks in the copy! If it is possible for an untrusted user to
1018 create their own symlink to any directory, the user could then (on a
1019 subsequent copy) replace the symlink with a real directory and affect the
1020 content of whatever directory the symlink references. For backup copies,
1021 you are better off using something like a bind mount instead of a symlink
1022 to modify your receiving hierarchy.
1024 See also bf(--copy-dirlinks) for an analogous option for the sending side.
1026 dit(bf(-H, --hard-links)) This tells rsync to look for hard-linked files in
1027 the source and link together the corresponding files on the destination.
1028 Without this option, hard-linked files in the source are treated
1029 as though they were separate files.
1031 This option does NOT necessarily ensure that the pattern of hard links on the
1032 destination exactly matches that on the source. Cases in which the
1033 destination may end up with extra hard links include the following:
1036 it() If the destination contains extraneous hard-links (more linking than
1037 what is present in the source file list), the copying algorithm will not
1038 break them explicitly. However, if one or more of the paths have content
1039 differences, the normal file-update process will break those extra links
1040 (unless you are using the bf(--inplace) option).
1041 it() If you specify a bf(--link-dest) directory that contains hard links,
1042 the linking of the destination files against the bf(--link-dest) files can
1043 cause some paths in the destination to become linked together due to the
1044 bf(--link-dest) associations.
1047 Note that rsync can only detect hard links between files that are inside
1048 the transfer set. If rsync updates a file that has extra hard-link
1049 connections to files outside the transfer, that linkage will be broken. If
1050 you are tempted to use the bf(--inplace) option to avoid this breakage, be
1051 very careful that you know how your files are being updated so that you are
1052 certain that no unintended changes happen due to lingering hard links (and
1053 see the bf(--inplace) option for more caveats).
1055 If incremental recursion is active (see bf(--recursive)), rsync may transfer
1056 a missing hard-linked file before it finds that another link for that contents
1057 exists elsewhere in the hierarchy. This does not affect the accuracy of
1058 the transfer (i.e. which files are hard-linked together), just its efficiency
1059 (i.e. copying the data for a new, early copy of a hard-linked file that could
1060 have been found later in the transfer in another member of the hard-linked
1061 set of files). One way to avoid this inefficiency is to disable
1062 incremental recursion using the bf(--no-inc-recursive) option.
1064 dit(bf(-p, --perms)) This option causes the receiving rsync to set the
1065 destination permissions to be the same as the source permissions. (See
1066 also the bf(--chmod) option for a way to modify what rsync considers to
1067 be the source permissions.)
1069 When this option is em(off), permissions are set as follows:
1072 it() Existing files (including updated files) retain their existing
1073 permissions, though the bf(--executability) option might change just
1074 the execute permission for the file.
1075 it() New files get their "normal" permission bits set to the source
1076 file's permissions masked with the receiving directory's default
1077 permissions (either the receiving process's umask, or the permissions
1078 specified via the destination directory's default ACL), and
1079 their special permission bits disabled except in the case where a new
1080 directory inherits a setgid bit from its parent directory.
1083 Thus, when bf(--perms) and bf(--executability) are both disabled,
1084 rsync's behavior is the same as that of other file-copy utilities,
1085 such as bf(cp)(1) and bf(tar)(1).
1087 In summary: to give destination files (both old and new) the source
1088 permissions, use bf(--perms). To give new files the destination-default
1089 permissions (while leaving existing files unchanged), make sure that the
1090 bf(--perms) option is off and use bf(--chmod=ugo=rwX) (which ensures that
1091 all non-masked bits get enabled). If you'd care to make this latter
1092 behavior easier to type, you could define a popt alias for it, such as
1093 putting this line in the file ~/.popt (the following defines the bf(-Z) option,
1094 and includes --no-g to use the default group of the destination dir):
1096 verb( rsync alias -Z --no-p --no-g --chmod=ugo=rwX)
1098 You could then use this new option in a command such as this one:
1100 verb( rsync -avZ src/ dest/)
1102 (Caveat: make sure that bf(-a) does not follow bf(-Z), or it will re-enable
1103 the two "--no-*" options mentioned above.)
1105 The preservation of the destination's setgid bit on newly-created
1106 directories when bf(--perms) is off was added in rsync 2.6.7. Older rsync
1107 versions erroneously preserved the three special permission bits for
1108 newly-created files when bf(--perms) was off, while overriding the
1109 destination's setgid bit setting on a newly-created directory. Default ACL
1110 observance was added to the ACL patch for rsync 2.6.7, so older (or
1111 non-ACL-enabled) rsyncs use the umask even if default ACLs are present.
1112 (Keep in mind that it is the version of the receiving rsync that affects
1115 dit(bf(-E, --executability)) This option causes rsync to preserve the
1116 executability (or non-executability) of regular files when bf(--perms) is
1117 not enabled. A regular file is considered to be executable if at least one
1118 'x' is turned on in its permissions. When an existing destination file's
1119 executability differs from that of the corresponding source file, rsync
1120 modifies the destination file's permissions as follows:
1123 it() To make a file non-executable, rsync turns off all its 'x'
1125 it() To make a file executable, rsync turns on each 'x' permission that
1126 has a corresponding 'r' permission enabled.
1129 If bf(--perms) is enabled, this option is ignored.
1131 dit(bf(-A, --acls)) This option causes rsync to update the destination
1132 ACLs to be the same as the source ACLs.
1133 The option also implies bf(--perms).
1135 The source and destination systems must have compatible ACL entries for this
1136 option to work properly. See the bf(--fake-super) option for a way to backup
1137 and restore ACLs that are not compatible.
1139 dit(bf(-X, --xattrs)) This option causes rsync to update the destination
1140 extended attributes to be the same as the source ones.
1142 For systems that support extended-attribute namespaces, a copy being done by a
1143 super-user copies all namespaces except system.*. A normal user only copies
1144 the user.* namespace. To be able to backup and restore non-user namespaces as
1145 a normal user, see the bf(--fake-super) option.
1147 The above name filtering can be overridden by using one or more filter options
1148 with the bf(x) modifier. When you specify an xattr-affecting filter rule, rsync
1149 requires that you do your own system/user filtering, as well as any additional
1150 filtering for what xattr names are copied and what names are allowed to be
1151 deleted. For example, to skip the system namespace, you could specify:
1153 quote(--filter='-x system.*')
1155 To skip all namespaces except the user namespace, you could specify a
1158 quote(--filter='-x! user.*')
1160 To prevent any attributes from being deleted, you could specify a receiver-only
1161 rule that excludes all names:
1163 quote(--filter='-xr *')
1165 Note that the bf(-X) option does not copy rsync's special xattr values (e.g.
1166 those used by bf(--fake-super)) unless you repeat the option (e.g. -XX).
1167 This "copy all xattrs" mode cannot be used with bf(--fake-super).
1169 dit(bf(--chmod)) This option tells rsync to apply one or more
1170 comma-separated "chmod" modes to the permission of the files in the
1171 transfer. The resulting value is treated as though it were the permissions
1172 that the sending side supplied for the file, which means that this option
1173 can seem to have no effect on existing files if bf(--perms) is not enabled.
1175 In addition to the normal parsing rules specified in the bf(chmod)(1)
1176 manpage, you can specify an item that should only apply to a directory by
1177 prefixing it with a 'D', or specify an item that should only apply to a
1178 file by prefixing it with a 'F'. For example, the following will ensure
1179 that all directories get marked set-gid, that no files are other-writable,
1180 that both are user-writable and group-writable, and that both have
1181 consistent executability across all bits:
1183 quote(--chmod=Dg+s,ug+w,Fo-w,+X)
1185 Using octal mode numbers is also allowed:
1187 quote(--chmod=D2775,F664)
1189 It is also legal to specify multiple bf(--chmod) options, as each
1190 additional option is just appended to the list of changes to make.
1192 See the bf(--perms) and bf(--executability) options for how the resulting
1193 permission value can be applied to the files in the transfer.
1195 dit(bf(-o, --owner)) This option causes rsync to set the owner of the
1196 destination file to be the same as the source file, but only if the
1197 receiving rsync is being run as the super-user (see also the bf(--super)
1198 and bf(--fake-super) options).
1199 Without this option, the owner of new and/or transferred files are set to
1200 the invoking user on the receiving side.
1202 The preservation of ownership will associate matching names by default, but
1203 may fall back to using the ID number in some circumstances (see also the
1204 bf(--numeric-ids) option for a full discussion).
1206 dit(bf(-g, --group)) This option causes rsync to set the group of the
1207 destination file to be the same as the source file. If the receiving
1208 program is not running as the super-user (or if bf(--no-super) was
1209 specified), only groups that the invoking user on the receiving side
1210 is a member of will be preserved.
1211 Without this option, the group is set to the default group of the invoking
1212 user on the receiving side.
1214 The preservation of group information will associate matching names by
1215 default, but may fall back to using the ID number in some circumstances
1216 (see also the bf(--numeric-ids) option for a full discussion).
1218 dit(bf(--devices)) This option causes rsync to transfer character and
1219 block device files to the remote system to recreate these devices.
1220 This option has no effect if the receiving rsync is not run as the
1221 super-user (see also the bf(--super) and bf(--fake-super) options).
1223 dit(bf(--specials)) This option causes rsync to transfer special files
1224 such as named sockets and fifos.
1226 dit(bf(-D)) The bf(-D) option is equivalent to bf(--devices) bf(--specials).
1228 dit(bf(--write-devices)) This tells rsync to treat a device on the receiving
1229 side as a regular file, allowing the writing of file data into a device.
1231 This option implies the bf(--inplace) option.
1233 Be careful using this, as you should know what devices are present on the
1234 receiving side of the transfer, especially if running rsync as root.
1236 This option is refused by an rsync daemon.
1238 dit(bf(-t, --times)) This tells rsync to transfer modification times along
1239 with the files and update them on the remote system. Note that if this
1240 option is not used, the optimization that excludes files that have not been
1241 modified cannot be effective; in other words, a missing bf(-t) or bf(-a) will
1242 cause the next transfer to behave as if it used bf(-I), causing all files to be
1243 updated (though rsync's delta-transfer algorithm will make the update fairly efficient
1244 if the files haven't actually changed, you're much better off using bf(-t)).
1246 dit(bf(-U, --atimes)) This tells rsync to set the access (use) times of the
1247 destination files to the same value as the source files.
1249 If repeated, it also sets the bf(--open-noatime) option, which can help you
1250 to make the sending and receiving systems have the same access times on the
1251 transferred files without needing to run rsync an extra time after a file is
1254 Note that some older rsync versions (prior to 3.2.0) may have been built with
1255 a pre-release bf(--atimes) patch that does not imply bf(--open-noatime) when
1256 this option is repeated.
1258 dit(bf(--open-noatime)) This tells rsync to open files with the O_NOATIME
1259 flag (on systems that support it) to avoid changing the access time of the
1260 files that are being transferred. If your OS does not support the O_NOATIME
1261 flag then rsync will silently ignore this option. Note also that some
1262 filesystems are mounted to avoid updating the atime on read access even
1263 without the O_NOATIME flag being set.
1265 dit(bf(-O, --omit-dir-times)) This tells rsync to omit directories when
1266 it is preserving modification times (see bf(--times)). If NFS is sharing
1267 the directories on the receiving side, it is a good idea to use bf(-O).
1268 This option is inferred if you use bf(--backup) without bf(--backup-dir).
1270 This option also has the side-effect of avoiding early creation of directories
1271 in incremental recursion copies. The default bf(--inc-recursive) copying
1272 normally does an early-create pass of all the sub-directories in a parent
1273 directory in order for it to be able to then set the modify time of the parent
1274 directory right away (without having to delay that until a bunch of recursive
1275 copying has finished). This early-create idiom is not necessary if directory
1276 modify times are not being preserved, so it is skipped. Since early-create
1277 directories don't have accurate mode, mtime, or ownership, the use of this
1278 option can help when someone wants to avoid these partially-finished
1281 dit(bf(-J, --omit-link-times)) This tells rsync to omit symlinks when
1282 it is preserving modification times (see bf(--times)).
1284 dit(bf(--super)) This tells the receiving side to attempt super-user
1285 activities even if the receiving rsync wasn't run by the super-user. These
1286 activities include: preserving users via the bf(--owner) option, preserving
1287 all groups (not just the current user's groups) via the bf(--groups)
1288 option, and copying devices via the bf(--devices) option. This is useful
1289 for systems that allow such activities without being the super-user, and
1290 also for ensuring that you will get errors if the receiving side isn't
1291 being run as the super-user. To turn off super-user activities, the
1292 super-user can use bf(--no-super).
1294 dit(bf(--fake-super)) When this option is enabled, rsync simulates
1295 super-user activities by saving/restoring the privileged attributes via
1296 special extended attributes that are attached to each file (as needed). This
1297 includes the file's owner and group (if it is not the default), the file's
1298 device info (device & special files are created as empty text files), and
1299 any permission bits that we won't allow to be set on the real file (e.g.
1300 the real file gets u-s,g-s,o-t for safety) or that would limit the owner's
1301 access (since the real super-user can always access/change a file, the
1302 files we create can always be accessed/changed by the creating user).
1303 This option also handles ACLs (if bf(--acls) was specified) and non-user
1304 extended attributes (if bf(--xattrs) was specified).
1306 This is a good way to backup data without using a super-user, and to store
1307 ACLs from incompatible systems.
1309 The bf(--fake-super) option only affects the side where the option is used.
1310 To affect the remote side of a remote-shell connection, use the
1311 bf(--remote-option) (bf(-M)) option:
1313 verb( rsync -av -M--fake-super /src/ host:/dest/)
1315 For a local copy, this option affects both the source and the destination.
1316 If you wish a local copy to enable this option just for the destination
1317 files, specify bf(-M--fake-super). If you wish a local copy to enable
1318 this option just for the source files, combine bf(--fake-super) with
1321 This option is overridden by both bf(--super) and bf(--no-super).
1323 See also the "fake super" setting in the daemon's rsyncd.conf file.
1325 dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
1326 up less space on the destination. If combined with bf(--inplace) the
1327 file created might not end up with sparse blocks with some combinations
1328 of kernel version and/or filesystem type. If bf(--whole-file) is in
1329 effect (e.g. for a local copy) then it will always work because rsync
1330 truncates the file prior to writing out the updated version.
1332 Note that versions of rsync older than 3.1.3 will reject the combination of
1333 bf(--sparse) and bf(--inplace).
1335 dit(bf(--preallocate)) This tells the receiver to allocate each destination
1336 file to its eventual size before writing data to the file. Rsync will only
1337 use the real filesystem-level preallocation support provided by Linux's
1338 bf(fallocate)(2) system call or Cygwin's bf(posix_fallocate)(3), not the slow
1339 glibc implementation that writes a null byte into each block.
1341 Without this option, larger files may not be entirely contiguous on the
1342 filesystem, but with this option rsync will probably copy more slowly. If the
1343 destination is not an extent-supporting filesystem (such as ext4, xfs, NTFS,
1344 etc.), this option may have no positive effect at all.
1346 If combined with bf(--sparse), the file will only have sparse blocks (as
1347 opposed to allocated sequences of null bytes) if the kernel version and
1348 filesystem type support creating holes in the allocated data.
1350 dit(bf(-n, --dry-run)) This makes rsync perform a trial run that doesn't
1351 make any changes (and produces mostly the same output as a real run). It
1352 is most commonly used in combination with the bf(-v, --verbose) and/or
1353 bf(-i, --itemize-changes) options to see what an rsync command is going
1354 to do before one actually runs it.
1356 The output of bf(--itemize-changes) is supposed to be exactly the same on a
1357 dry run and a subsequent real run (barring intentional trickery and system
1358 call failures); if it isn't, that's a bug. Other output should be mostly
1359 unchanged, but may differ in some areas. Notably, a dry run does not
1360 send the actual data for file transfers, so bf(--progress) has no effect,
1361 the "bytes sent", "bytes received", "literal data", and "matched data"
1362 statistics are too small, and the "speedup" value is equivalent to a run
1363 where no file transfers were needed.
1365 dit(bf(-W, --whole-file)) This option disables rsync's delta-transfer algorithm,
1366 which causes all transferred files to be sent whole. The transfer may be
1367 faster if this option is used when the bandwidth between the source and
1368 destination machines is higher than the bandwidth to disk (especially when the
1369 "disk" is actually a networked filesystem). This is the default when both
1370 the source and destination are specified as local paths, but only if no
1371 batch-writing option is in effect.
1373 dit(bf(--checksum-choice=STR)) This option overrides the checksum algorithms.
1374 If one algorithm name is specified, it is used for both the transfer checksums
1375 and (assuming bf(--checksum) is specified) the pre-transfer checksums. If two
1376 comma-separated names are supplied, the first name affects the transfer
1377 checksums, and the second name affects the pre-transfer checksums (bf(-c)).
1379 The algorithm choices are "auto", "xxhash", "MD5", "MD4", and "none".
1381 If "none" is specified for the first (or only) name, the bf(--whole-file) option
1382 is forced on and no checksum verification is performed on the transferred data.
1383 If "none" is specified for the second (or only) name, the bf(--checksum) option
1386 The "auto" option is the default, where rsync bases its algorithm choice on a
1387 negotation between the client and the server as follows:
1389 If both the client and the server are at least version 3.2.0, they will
1390 exchange a list of checksum names and choose the first one in the list that
1391 they have in common.
1392 This typically means that they will choose xxhash if they both support it
1393 and fall back to MD5.
1394 If one side of the transfer is not new enough to support this checksum
1395 negotation, then a value is chosen based on the protocol version (which
1396 chooses between MD5 and various flavors of MD4 based on protocol age).
1398 You can also override the checksum using the RSYNC_CHECKSUM_LIST environment
1399 variable by setting it to a space-separated list of checksum names that you
1400 consider acceptable. If no common checksum is found, the client exits with an
1401 error. This method does not allow you to specify the transfer checksum
1402 separately from the pre-transfer checksum, and it ignores "auto" and all
1403 unknown checksum names. If the remote rsync is not new enough to handle a
1404 checksum negotiation list, the list is silently ignored unless it contains the
1405 string "FAIL" in it.
1407 The use of the bf(--checksum-choice) option overrides this environment list.
1409 dit(bf(-x, --one-file-system)) This tells rsync to avoid crossing a
1410 filesystem boundary when recursing. This does not limit the user's ability
1411 to specify items to copy from multiple filesystems, just rsync's recursion
1412 through the hierarchy of each directory that the user specified, and also
1413 the analogous recursion on the receiving side during deletion. Also keep
1414 in mind that rsync treats a "bind" mount to the same device as being on the
1417 If this option is repeated, rsync omits all mount-point directories from
1418 the copy. Otherwise, it includes an empty directory at each mount-point it
1419 encounters (using the attributes of the mounted directory because those of
1420 the underlying mount-point directory are inaccessible).
1422 If rsync has been told to collapse symlinks (via bf(--copy-links) or
1423 bf(--copy-unsafe-links)), a symlink to a directory on another device is
1424 treated like a mount-point. Symlinks to non-directories are unaffected
1430 dit(bf(--existing, --ignore-non-existing)) This tells rsync to skip
1431 creating files (including directories) that do not exist
1432 yet on the destination. If this option is
1433 combined with the bf(--ignore-existing) option, no files will be updated
1434 (which can be useful if all you want to do is delete extraneous files).
1436 This option is a transfer rule, not an exclude, so it doesn't affect the
1437 data that goes into the file-lists, and thus it doesn't affect deletions.
1438 It just limits the files that the receiver requests to be transferred.
1440 dit(bf(--ignore-existing)) This tells rsync to skip updating files that
1441 already exist on the destination (this does em(not) ignore existing
1442 directories, or nothing would get done). See also bf(--existing).
1444 This option is a transfer rule, not an exclude, so it doesn't affect the
1445 data that goes into the file-lists, and thus it doesn't affect deletions.
1446 It just limits the files that the receiver requests to be transferred.
1448 This option can be useful for those doing backups using the bf(--link-dest)
1449 option when they need to continue a backup run that got interrupted. Since
1450 a bf(--link-dest) run is copied into a new directory hierarchy (when it is
1451 used properly), using bf(--ignore-existing) will ensure that the
1452 already-handled files don't get tweaked (which avoids a change in
1453 permissions on the hard-linked files). This does mean that this option
1454 is only looking at the existing files in the destination hierarchy itself.
1456 dit(bf(--remove-source-files)) This tells rsync to remove from the sending
1457 side the files (meaning non-directories) that are a part of the transfer
1458 and have been successfully duplicated on the receiving side.
1460 Note that you should only use this option on source files that are quiescent.
1461 If you are using this to move files that show up in a particular directory over
1462 to another host, make sure that the finished files get renamed into the source
1463 directory, not directly written into it, so that rsync can't possibly transfer
1464 a file that is not yet fully written. If you can't first write the files into
1465 a different directory, you should use a naming idiom that lets rsync avoid
1466 transferring files that are not yet finished (e.g. name the file "foo.new" when
1467 it is written, rename it to "foo" when it is done, and then use the option
1468 bf(--exclude='*.new') for the rsync transfer).
1470 Starting with 3.1.0, rsync will skip the sender-side removal (and output an
1471 error) if the file's size or modify time has not stayed unchanged.
1473 dit(bf(--delete)) This tells rsync to delete extraneous files from the
1474 receiving side (ones that aren't on the sending side), but only for the
1475 directories that are being synchronized. You must have asked rsync to
1476 send the whole directory (e.g. "dir" or "dir/") without using a wildcard
1477 for the directory's contents (e.g. "dir/*") since the wildcard is expanded
1478 by the shell and rsync thus gets a request to transfer individual files, not
1479 the files' parent directory. Files that are excluded from the transfer are
1480 also excluded from being deleted unless you use the bf(--delete-excluded)
1481 option or mark the rules as only matching on the sending side (see the
1482 include/exclude modifiers in the FILTER RULES section).
1484 Prior to rsync 2.6.7, this option would have no effect unless bf(--recursive)
1485 was enabled. Beginning with 2.6.7, deletions will also occur when bf(--dirs)
1486 (bf(-d)) is enabled, but only for directories whose contents are being copied.
1488 This option can be dangerous if used incorrectly! It is a very good idea to
1489 first try a run using the bf(--dry-run) option (bf(-n)) to see what files are
1490 going to be deleted.
1492 If the sending side detects any I/O errors, then the deletion of any
1493 files at the destination will be automatically disabled. This is to
1494 prevent temporary filesystem failures (such as NFS errors) on the
1495 sending side from causing a massive deletion of files on the
1496 destination. You can override this with the bf(--ignore-errors) option.
1498 The bf(--delete) option may be combined with one of the --delete-WHEN options
1499 without conflict, as well as bf(--delete-excluded). However, if none of the
1500 --delete-WHEN options are specified, rsync will choose the
1501 bf(--delete-during) algorithm when talking to rsync 3.0.0 or newer, and
1502 the bf(--delete-before) algorithm when talking to an older rsync. See also
1503 bf(--delete-delay) and bf(--delete-after).
1505 dit(bf(--delete-before)) Request that the file-deletions on the receiving
1506 side be done before the transfer starts.
1507 See bf(--delete) (which is implied) for more details on file-deletion.
1509 Deleting before the transfer is helpful if the filesystem is tight for space
1510 and removing extraneous files would help to make the transfer possible.
1511 However, it does introduce a delay before the start of the transfer,
1512 and this delay might cause the transfer to timeout (if bf(--timeout) was
1513 specified). It also forces rsync to use the old, non-incremental recursion
1514 algorithm that requires rsync to scan all the files in the transfer into
1515 memory at once (see bf(--recursive)).
1517 dit(bf(--delete-during, --del)) Request that the file-deletions on the
1518 receiving side be done incrementally as the transfer happens. The
1519 per-directory delete scan is done right before each directory is checked
1520 for updates, so it behaves like a more efficient bf(--delete-before),
1521 including doing the deletions prior to any per-directory filter files
1522 being updated. This option was first added in rsync version 2.6.4.
1523 See bf(--delete) (which is implied) for more details on file-deletion.
1525 dit(bf(--delete-delay)) Request that the file-deletions on the receiving
1526 side be computed during the transfer (like bf(--delete-during)), and then
1527 removed after the transfer completes. This is useful when combined with
1528 bf(--delay-updates) and/or bf(--fuzzy), and is more efficient than using
1529 bf(--delete-after) (but can behave differently, since bf(--delete-after)
1530 computes the deletions in a separate pass after all updates are done).
1531 If the number of removed files overflows an internal buffer, a
1532 temporary file will be created on the receiving side to hold the names (it
1533 is removed while open, so you shouldn't see it during the transfer). If
1534 the creation of the temporary file fails, rsync will try to fall back to
1535 using bf(--delete-after) (which it cannot do if bf(--recursive) is doing an
1537 See bf(--delete) (which is implied) for more details on file-deletion.
1539 dit(bf(--delete-after)) Request that the file-deletions on the receiving
1540 side be done after the transfer has completed. This is useful if you
1541 are sending new per-directory merge files as a part of the transfer and
1542 you want their exclusions to take effect for the delete phase of the
1543 current transfer. It also forces rsync to use the old, non-incremental
1544 recursion algorithm that requires rsync to scan all the files in the
1545 transfer into memory at once (see bf(--recursive)).
1546 See bf(--delete) (which is implied) for more details on file-deletion.
1548 dit(bf(--delete-excluded)) In addition to deleting the files on the
1549 receiving side that are not on the sending side, this tells rsync to also
1550 delete any files on the receiving side that are excluded (see bf(--exclude)).
1551 See the FILTER RULES section for a way to make individual exclusions behave
1552 this way on the receiver, and for a way to protect files from
1553 bf(--delete-excluded).
1554 See bf(--delete) (which is implied) for more details on file-deletion.
1556 dit(bf(--ignore-missing-args)) When rsync is first processing the explicitly
1557 requested source files (e.g. command-line arguments or bf(--files-from)
1558 entries), it is normally an error if the file cannot be found. This option
1559 suppresses that error, and does not try to transfer the file. This does not
1560 affect subsequent vanished-file errors if a file was initially found to be
1561 present and later is no longer there.
1563 dit(bf(--delete-missing-args)) This option takes the behavior of (the implied)
1564 bf(--ignore-missing-args) option a step farther: each missing arg will become
1565 a deletion request of the corresponding destination file on the receiving side
1566 (should it exist). If the destination file is a non-empty directory, it will
1567 only be successfully deleted if --force or --delete are in effect. Other than
1568 that, this option is independent of any other type of delete processing.
1570 The missing source files are represented by special file-list entries which
1571 display as a "*missing" entry in the bf(--list-only) output.
1573 dit(bf(--ignore-errors)) Tells bf(--delete) to go ahead and delete files
1574 even when there are I/O errors.
1576 dit(bf(--force)) This option tells rsync to delete a non-empty directory
1577 when it is to be replaced by a non-directory. This is only relevant if
1578 deletions are not active (see bf(--delete) for details).
1580 Note for older rsync versions: bf(--force) used to still be required when
1581 using bf(--delete-after), and it used to be non-functional unless the
1582 bf(--recursive) option was also enabled.
1584 dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM
1585 files or directories. If that limit is exceeded, all further deletions are
1586 skipped through the end of the transfer. At the end, rsync outputs a warning
1587 (including a count of the skipped deletions) and exits with an error code
1588 of 25 (unless some more important error condition also occurred).
1590 Beginning with version 3.0.0, you may specify bf(--max-delete=0) to be warned
1591 about any extraneous files in the destination without removing any of them.
1592 Older clients interpreted this as "unlimited", so if you don't know what
1593 version the client is, you can use the less obvious bf(--max-delete=-1) as
1594 a backward-compatible way to specify that no deletions be allowed (though
1595 really old versions didn't warn when the limit was exceeded).
1597 dit(bf(--max-size=SIZE)) This tells rsync to avoid transferring any
1598 file that is larger than the specified SIZE. The SIZE value can be
1599 suffixed with a string to indicate a size multiplier, and
1600 may be a fractional value (e.g. "bf(--max-size=1.5m)").
1602 This option is a transfer rule, not an exclude, so it doesn't affect the
1603 data that goes into the file-lists, and thus it doesn't affect deletions.
1604 It just limits the files that the receiver requests to be transferred.
1606 The suffixes are as follows: "K" (or "KiB") is a kibibyte (1024),
1607 "M" (or "MiB") is a mebibyte (1024*1024), and "G" (or "GiB") is a
1608 gibibyte (1024*1024*1024).
1609 If you want the multiplier to be 1000 instead of 1024, use "KB",
1610 "MB", or "GB". (Note: lower-case is also accepted for all values.)
1611 Finally, if the suffix ends in either "+1" or "-1", the value will
1612 be offset by one byte in the indicated direction.
1614 Examples: --max-size=1.5mb-1 is 1499999 bytes, and --max-size=2g+1 is
1617 Note that rsync versions prior to 3.1.0 did not allow bf(--max-size=0).
1619 dit(bf(--min-size=SIZE)) This tells rsync to avoid transferring any
1620 file that is smaller than the specified SIZE, which can help in not
1621 transferring small, junk files.
1622 See the bf(--max-size) option for a description of SIZE and other information.
1624 Note that rsync versions prior to 3.1.0 did not allow bf(--min-size=0).
1626 dit(bf(-B, --block-size=BLOCKSIZE)) This forces the block size used in
1627 rsync's delta-transfer algorithm to a fixed value. It is normally selected based on
1628 the size of each file being updated. See the technical report for details.
1630 dit(bf(-e, --rsh=COMMAND)) This option allows you to choose an alternative
1631 remote shell program to use for communication between the local and
1632 remote copies of rsync. Typically, rsync is configured to use ssh by
1633 default, but you may prefer to use rsh on a local network.
1635 If this option is used with bf([user@]host::module/path), then the
1636 remote shell em(COMMAND) will be used to run an rsync daemon on the
1637 remote host, and all data will be transmitted through that remote
1638 shell connection, rather than through a direct socket connection to a
1639 running rsync daemon on the remote host. See the section "USING
1640 RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" above.
1642 Beginning with rsync 3.2.0, the RSYNC_PORT environment variable will be
1643 set when a daemon connection is being made via a remote-shell
1644 connection. It is set to 0 if the default daemon port is being assumed,
1645 or it is set to the value of the rsync port that was specified via
1646 either the bf(--port) option or a non-empty port value in an rsync://
1647 URL. This allows the script to discern if a non-default port is being
1648 requested, allowing for things such as an SSL or stunnel helper script
1649 to connect to a default or alternate port.
1651 Command-line arguments are permitted in COMMAND provided that COMMAND is
1652 presented to rsync as a single argument. You must use spaces (not tabs
1653 or other whitespace) to separate the command and args from each other,
1654 and you can use single- and/or double-quotes to preserve spaces in an
1655 argument (but not backslashes). Note that doubling a single-quote
1656 inside a single-quoted string gives you a single-quote; likewise for
1657 double-quotes (though you need to pay attention to which quotes your
1658 shell is parsing and which quotes rsync is parsing). Some examples:
1660 verb( -e 'ssh -p 2234')
1661 verb( -e 'ssh -o "ProxyCommand nohup ssh firewall nc -w1 %h %p"')
1663 (Note that ssh users can alternately customize site-specific connect
1664 options in their .ssh/config file.)
1666 You can also choose the remote shell program using the RSYNC_RSH
1667 environment variable, which accepts the same range of values as bf(-e).
1669 See also the bf(--blocking-io) option which is affected by this option.
1671 dit(bf(--rsync-path=PROGRAM)) Use this to specify what program is to be run
1672 on the remote machine to start-up rsync. Often used when rsync is not in
1673 the default remote-shell's path (e.g. --rsync-path=/usr/local/bin/rsync).
1674 Note that PROGRAM is run with the help of a shell, so it can be any
1675 program, script, or command sequence you'd care to run, so long as it does
1676 not corrupt the standard-in & standard-out that rsync is using to
1679 One tricky example is to set a different default directory on the remote
1680 machine for use with the bf(--relative) option. For instance:
1682 verb( rsync -avR --rsync-path="cd /a/b && rsync" host:c/d /e/)
1684 dit(bf(-M, --remote-option=OPTION)) This option is used for more advanced
1685 situations where you want certain effects to be limited to one side of the
1686 transfer only. For instance, if you want to pass bf(--log-file=FILE) and
1687 bf(--fake-super) to the remote system, specify it like this:
1689 verb( rsync -av -M --log-file=foo -M--fake-super src/ dest/)
1691 If you want to have an option affect only the local side of a transfer when
1692 it normally affects both sides, send its negation to the remote side. Like
1695 verb( rsync -av -x -M--no-x src/ dest/)
1697 Be cautious using this, as it is possible to toggle an option that will cause
1698 rsync to have a different idea about what data to expect next over the socket,
1699 and that will make it fail in a cryptic fashion.
1701 Note that it is best to use a separate bf(--remote-option) for each option you
1702 want to pass. This makes your usage compatible with the bf(--protect-args)
1703 option. If that option is off, any spaces in your remote options will be split
1704 by the remote shell unless you take steps to protect them.
1706 When performing a local transfer, the "local" side is the sender and the
1707 "remote" side is the receiver.
1709 Note some versions of the popt option-parsing library have a bug in them that
1710 prevents you from using an adjacent arg with an equal in it next to a short
1711 option letter (e.g. tt(-M--log-file=/tmp/foo)). If this bug affects your
1712 version of popt, you can use the version of popt that is included with rsync.
1714 dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
1715 broad range of files that you often don't want to transfer between
1716 systems. It uses a similar algorithm to CVS to determine if
1717 a file should be ignored.
1719 The exclude list is initialized to exclude the following items (these
1720 initial items are marked as perishable -- see the FILTER RULES section):
1722 quote(quote(tt(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
1723 .nse_depinfo *~ #* .#* ,* _$* *$ *.old *.bak *.BAK *.orig *.rej .del-*
1724 *.a *.olb *.o *.obj *.so *.exe *.Z *.elc *.ln core .svn/ .git/ .hg/ .bzr/)))
1726 then, files listed in a $HOME/.cvsignore are added to the list and any
1727 files listed in the CVSIGNORE environment variable (all cvsignore names
1728 are delimited by whitespace).
1730 Finally, any file is ignored if it is in the same directory as a
1731 .cvsignore file and matches one of the patterns listed therein. Unlike
1732 rsync's filter/exclude files, these patterns are split on whitespace.
1733 See the bf(cvs)(1) manual for more information.
1735 If you're combining bf(-C) with your own bf(--filter) rules, you should
1736 note that these CVS excludes are appended at the end of your own rules,
1737 regardless of where the bf(-C) was placed on the command-line. This makes them
1738 a lower priority than any rules you specified explicitly. If you want to
1739 control where these CVS excludes get inserted into your filter rules, you
1740 should omit the bf(-C) as a command-line option and use a combination of
1741 bf(--filter=:C) and bf(--filter=-C) (either on your command-line or by
1742 putting the ":C" and "-C" rules into a filter file with your other rules).
1743 The first option turns on the per-directory scanning for the .cvsignore
1744 file. The second option does a one-time import of the CVS excludes
1747 dit(bf(-f, --filter=RULE)) This option allows you to add rules to selectively
1748 exclude certain files from the list of files to be transferred. This is
1749 most useful in combination with a recursive transfer.
1751 You may use as many bf(--filter) options on the command line as you like
1752 to build up the list of files to exclude. If the filter contains whitespace,
1753 be sure to quote it so that the shell gives the rule to rsync as a single
1754 argument. The text below also mentions that you can use an underscore to
1755 replace the space that separates a rule from its arg.
1757 See the FILTER RULES section for detailed information on this option.
1759 dit(bf(-F)) The bf(-F) option is a shorthand for adding two bf(--filter) rules to
1760 your command. The first time it is used is a shorthand for this rule:
1762 verb( --filter='dir-merge /.rsync-filter')
1764 This tells rsync to look for per-directory .rsync-filter files that have
1765 been sprinkled through the hierarchy and use their rules to filter the
1766 files in the transfer. If bf(-F) is repeated, it is a shorthand for this
1769 verb( --filter='exclude .rsync-filter')
1771 This filters out the .rsync-filter files themselves from the transfer.
1773 See the FILTER RULES section for detailed information on how these options
1776 dit(bf(--exclude=PATTERN)) This option is a simplified form of the
1777 bf(--filter) option that defaults to an exclude rule and does not allow
1778 the full rule-parsing syntax of normal filter rules.
1780 See the FILTER RULES section for detailed information on this option.
1782 dit(bf(--exclude-from=FILE)) This option is related to the bf(--exclude)
1783 option, but it specifies a FILE that contains exclude patterns (one per line).
1784 Blank lines in the file and lines starting with ';' or '#' are ignored.
1785 If em(FILE) is bf(-), the list will be read from standard input.
1787 dit(bf(--include=PATTERN)) This option is a simplified form of the
1788 bf(--filter) option that defaults to an include rule and does not allow
1789 the full rule-parsing syntax of normal filter rules.
1791 See the FILTER RULES section for detailed information on this option.
1793 dit(bf(--include-from=FILE)) This option is related to the bf(--include)
1794 option, but it specifies a FILE that contains include patterns (one per line).
1795 Blank lines in the file and lines starting with ';' or '#' are ignored.
1796 If em(FILE) is bf(-), the list will be read from standard input.
1798 dit(bf(--files-from=FILE)) Using this option allows you to specify the
1799 exact list of files to transfer (as read from the specified FILE or bf(-)
1800 for standard input). It also tweaks the default behavior of rsync to make
1801 transferring just the specified files and directories easier:
1804 it() The bf(--relative) (bf(-R)) option is implied, which preserves the path
1805 information that is specified for each item in the file (use
1806 bf(--no-relative) or bf(--no-R) if you want to turn that off).
1807 it() The bf(--dirs) (bf(-d)) option is implied, which will create directories
1808 specified in the list on the destination rather than noisily skipping
1809 them (use bf(--no-dirs) or bf(--no-d) if you want to turn that off).
1810 it() The bf(--archive) (bf(-a)) option's behavior does not imply bf(--recursive)
1811 (bf(-r)), so specify it explicitly, if you want it.
1812 it() These side-effects change the default state of rsync, so the position
1813 of the bf(--files-from) option on the command-line has no bearing on how
1814 other options are parsed (e.g. bf(-a) works the same before or after
1815 bf(--files-from), as does bf(--no-R) and all other options).
1818 The filenames that are read from the FILE are all relative to the
1819 source dir -- any leading slashes are removed and no ".." references are
1820 allowed to go higher than the source dir. For example, take this
1823 verb( rsync -a --files-from=/tmp/foo /usr remote:/backup)
1825 If /tmp/foo contains the string "bin" (or even "/bin"), the /usr/bin
1826 directory will be created as /backup/bin on the remote host. If it
1827 contains "bin/" (note the trailing slash), the immediate contents of
1828 the directory would also be sent (without needing to be explicitly
1829 mentioned in the file -- this began in version 2.6.4). In both cases,
1830 if the bf(-r) option was enabled, that dir's entire hierarchy would
1831 also be transferred (keep in mind that bf(-r) needs to be specified
1832 explicitly with bf(--files-from), since it is not implied by bf(-a)).
1834 that the effect of the (enabled by default) bf(--relative) option is to
1835 duplicate only the path info that is read from the file -- it does not
1836 force the duplication of the source-spec path (/usr in this case).
1838 In addition, the bf(--files-from) file can be read from the remote host
1839 instead of the local host if you specify a "host:" in front of the file
1840 (the host must match one end of the transfer). As a short-cut, you can
1841 specify just a prefix of ":" to mean "use the remote end of the
1842 transfer". For example:
1844 verb( rsync -a --files-from=:/path/file-list src:/ /tmp/copy)
1846 This would copy all the files specified in the /path/file-list file that
1847 was located on the remote "src" host.
1849 If the bf(--iconv) and bf(--protect-args) options are specified and the
1850 bf(--files-from) filenames are being sent from one host to another, the
1851 filenames will be translated from the sending host's charset to the
1852 receiving host's charset.
1854 NOTE: sorting the list of files in the --files-from input helps rsync to be
1855 more efficient, as it will avoid re-visiting the path elements that are shared
1856 between adjacent entries. If the input is not sorted, some path elements
1857 (implied directories) may end up being scanned multiple times, and rsync will
1858 eventually unduplicate them after they get turned into file-list elements.
1863 dit(bf(-0, --from0)) This tells rsync that the rules/filenames it reads from a
1864 file are terminated by a null ('\0') character, not a NL, CR, or CR+LF.
1865 This affects bf(--exclude-from), bf(--include-from), bf(--files-from), and any
1866 merged files specified in a bf(--filter) rule.
1867 It does not affect bf(--cvs-exclude) (since all names read from a .cvsignore
1868 file are split on whitespace).
1870 dit(bf(-s, --protect-args)) This option sends all filenames and most options to
1871 the remote rsync without allowing the remote shell to interpret them. This
1872 means that spaces are not split in names, and any non-wildcard special
1873 characters are not translated (such as ~, $, ;, &, etc.). Wildcards are
1874 expanded on the remote host by rsync (instead of the shell doing it).
1876 If you use this option with bf(--iconv), the args related to the remote
1877 side will also be translated
1878 from the local to the remote character-set. The translation happens before
1879 wild-cards are expanded. See also the bf(--files-from) option.
1881 You may also control this option via the RSYNC_PROTECT_ARGS environment
1882 variable. If this variable has a non-zero value, this option will be enabled
1883 by default, otherwise it will be disabled by default. Either state is
1884 overridden by a manually specified positive or negative version of this option
1885 (note that bf(--no-s) and bf(--no-protect-args) are the negative versions).
1886 Since this option was first introduced in 3.0.0, you'll need to make sure it's
1887 disabled if you ever need to interact with a remote rsync that is older than
1890 Rsync can also be configured (at build time) to have this option enabled by
1891 default (with is overridden by both the environment and the command-line).
1892 This option will eventually become a new default setting at some
1893 as-yet-undetermined point in the future.
1895 dit(bf(--copy-as=USER[:GROUP])) This option instructs rsync to use the USER and
1896 (if specified after a colon) the GROUP for the copy operations. This only works
1897 if the user that is running rsync has the ability to change users. If the group
1898 is not specified then the user's default groups are used.
1900 The option only affects one side of the transfer unless the transfer is local,
1901 in which case it affects both sides. Use the bf(--remote-option) to affect the
1902 remote side, such as bf(-M--copy-as=joe). For a local transfer, the "lsh"
1903 support file provides a local-shell helper script that can be used to allow a
1904 "localhost:" host-spec to be specified without needing to setup any remote
1905 shells (allowing you to specify remote options that affect the side of the
1906 transfer that is using the host-spec, and local options for the other side).
1908 This option can help to reduce the risk of an rsync being run as root into or
1909 out of a directory that might have live changes happening to it and you want to
1910 make sure that root-level read or write actions of system files are not
1911 possible. While you could alternatively run all of rsync as the specified user,
1912 sometimes you need the root-level host-access credentials to be used, so this
1913 allows rsync to drop root for the copying part of the operation after the
1914 remote-shell or daemon connection is established.
1916 For example, the following rsync writes the local files as user "joe":
1918 verb( sudo rsync -aiv --copy-as=joe host1:backups/joe/ /home/joe/)
1920 This makes all files owned by user "joe", limits the groups to those that are
1921 available to that user, and makes it impossible for the joe user to do a timed
1922 exploit of the path to induce a change to a file that the joe user has no
1923 permissions to change.
1925 dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a
1926 scratch directory when creating temporary copies of the files transferred
1927 on the receiving side. The default behavior is to create each temporary
1928 file in the same directory as the associated destination file.
1929 Beginning with rsync 3.1.1, the temp-file names inside the specified DIR will
1930 not be prefixed with an extra dot (though they will still have a random suffix
1933 This option is most often used when the receiving disk partition does not
1934 have enough free space to hold a copy of the largest file in the transfer.
1935 In this case (i.e. when the scratch directory is on a different disk
1936 partition), rsync will not be able to rename each received temporary file
1937 over the top of the associated destination file, but instead must copy it
1938 into place. Rsync does this by copying the file over the top of the
1939 destination file, which means that the destination file will contain
1940 truncated data during this copy. If this were not done this way (even if
1941 the destination file were first removed, the data locally copied to a
1942 temporary file in the destination directory, and then renamed into place)
1943 it would be possible for the old file to continue taking up disk space (if
1944 someone had it open), and thus there might not be enough room to fit the
1945 new version on the disk at the same time.
1947 If you are using this option for reasons other than a shortage of disk
1948 space, you may wish to combine it with the bf(--delay-updates) option,
1949 which will ensure that all copied files get put into subdirectories in the
1950 destination hierarchy, awaiting the end of the transfer. If you don't
1951 have enough room to duplicate all the arriving files on the destination
1952 partition, another way to tell rsync that you aren't overly concerned
1953 about disk space is to use the bf(--partial-dir) option with a relative
1954 path; because this tells rsync that it is OK to stash off a copy of a
1955 single file in a subdir in the destination hierarchy, rsync will use the
1956 partial-dir as a staging area to bring over the copied file, and then
1957 rename it into place from there. (Specifying a bf(--partial-dir) with
1958 an absolute path does not have this side-effect.)
1960 dit(bf(-y, --fuzzy)) This option tells rsync that it should look for a
1961 basis file for any destination file that is missing. The current algorithm
1962 looks in the same directory as the destination file for either a file that
1963 has an identical size and modified-time, or a similarly-named file. If
1964 found, rsync uses the fuzzy basis file to try to speed up the transfer.
1966 If the option is repeated, the fuzzy scan will also be done in any matching
1967 alternate destination directories that are specified via bf(--compare-dest),
1968 bf(--copy-dest), or bf(--link-dest).
1970 Note that the use of the bf(--delete) option might get rid of any potential
1971 fuzzy-match files, so either use bf(--delete-after) or specify some
1972 filename exclusions if you need to prevent this.
1974 dit(bf(--compare-dest=DIR)) This option instructs rsync to use em(DIR) on
1975 the destination machine as an additional hierarchy to compare destination
1976 files against doing transfers (if the files are missing in the destination
1977 directory). If a file is found in em(DIR) that is identical to the
1978 sender's file, the file will NOT be transferred to the destination
1979 directory. This is useful for creating a sparse backup of just files that
1980 have changed from an earlier backup.
1981 This option is typically used to copy into an empty (or newly created)
1984 Beginning in version 2.6.4, multiple bf(--compare-dest) directories may be
1985 provided, which will cause rsync to search the list in the order specified
1987 If a match is found that differs only in attributes, a local copy is made
1988 and the attributes updated.
1989 If a match is not found, a basis file from one of the em(DIR)s will be
1990 selected to try to speed up the transfer.
1992 If em(DIR) is a relative path, it is relative to the destination directory.
1993 See also bf(--copy-dest) and bf(--link-dest).
1995 NOTE: beginning with version 3.1.0, rsync will remove a file from a non-empty
1996 destination hierarchy if an exact match is found in one of the compare-dest
1997 hierarchies (making the end result more closely match a fresh copy).
1999 dit(bf(--copy-dest=DIR)) This option behaves like bf(--compare-dest), but
2000 rsync will also copy unchanged files found in em(DIR) to the destination
2001 directory using a local copy.
2002 This is useful for doing transfers to a new destination while leaving
2003 existing files intact, and then doing a flash-cutover when all files have
2004 been successfully transferred.
2006 Multiple bf(--copy-dest) directories may be provided, which will cause
2007 rsync to search the list in the order specified for an unchanged file.
2008 If a match is not found, a basis file from one of the em(DIR)s will be
2009 selected to try to speed up the transfer.
2011 If em(DIR) is a relative path, it is relative to the destination directory.
2012 See also bf(--compare-dest) and bf(--link-dest).
2014 dit(bf(--link-dest=DIR)) This option behaves like bf(--copy-dest), but
2015 unchanged files are hard linked from em(DIR) to the destination directory.
2016 The files must be identical in all preserved attributes (e.g. permissions,
2017 possibly ownership) in order for the files to be linked together.
2020 verb( rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/)
2022 If file's aren't linking, double-check their attributes. Also check if some
2023 attributes are getting forced outside of rsync's control, such a mount option
2024 that squishes root to a single user, or mounts a removable drive with generic
2025 ownership (such as OS X's "Ignore ownership on this volume" option).
2027 Beginning in version 2.6.4, multiple bf(--link-dest) directories may be
2028 provided, which will cause rsync to search the list in the order specified
2029 for an exact match (there is a limit of 20 such directories).
2030 If a match is found that differs only in attributes, a local copy is made
2031 and the attributes updated.
2032 If a match is not found, a basis file from one of the em(DIR)s will be
2033 selected to try to speed up the transfer.
2035 This option works best when copying into an empty destination hierarchy, as
2036 existing files may get their attributes tweaked, and that can affect alternate
2037 destination files via hard-links. Also, itemizing of changes can get a bit
2038 muddled. Note that prior to version 3.1.0, an alternate-directory exact match
2039 would never be found (nor linked into the destination) when a destination file
2042 Note that if you combine this option with bf(--ignore-times), rsync will not
2043 link any files together because it only links identical files together as a
2044 substitute for transferring the file, never as an additional check after the
2047 If em(DIR) is a relative path, it is relative to the destination directory.
2048 See also bf(--compare-dest) and bf(--copy-dest).
2050 Note that rsync versions prior to 2.6.1 had a bug that could prevent
2051 bf(--link-dest) from working properly for a non-super-user when bf(-o) was
2052 specified (or implied by bf(-a)). You can work-around this bug by avoiding
2053 the bf(-o) option when sending to an old rsync.
2055 dit(bf(-z, --compress)) With this option, rsync compresses the file data
2056 as it is sent to the destination machine, which reduces the amount of data
2057 being transmitted -- something that is useful over a slow connection.
2059 Note that this option typically achieves better compression ratios than can
2060 be achieved by using a compressing remote shell or a compressing transport
2061 because it takes advantage of the implicit information in the matching data
2062 blocks that are not explicitly sent over the connection. This matching-data
2063 compression comes at a cost of CPU, though, and can be disabled by repeating
2064 the bf(-z) option, but only if both sides are at least version 3.1.1.
2066 Note that if your version of rsync was compiled with an external zlib (instead
2067 of the zlib that comes packaged with rsync) then it will not support the
2068 old-style compression, only the new-style (repeated-option) compression. In
2069 the future this new-style compression will likely become the default.
2071 The client rsync requests new-style compression on the server via the
2072 bf(--new-compress) option, so if you see that option rejected it means that
2073 the server is not new enough to support bf(-zz). Rsync also accepts the
2074 bf(--old-compress) option for a future time when new-style compression
2075 becomes the default.
2077 See the bf(--skip-compress) option for the default list of file suffixes
2078 that will not be compressed.
2080 dit(bf(--compress-level=NUM)) Explicitly set the compression level to use
2081 (see bf(--compress)) instead of letting it default. If NUM is non-zero,
2082 the bf(--compress) option is implied.
2084 dit(bf(--skip-compress=LIST)) Override the list of file suffixes that will
2085 not be compressed. The bf(LIST) should be one or more file suffixes
2086 (without the dot) separated by slashes (/).
2088 You may specify an empty string to indicate that no file should be skipped.
2090 Simple character-class matching is supported: each must consist of a list
2091 of letters inside the square brackets (e.g. no special classes, such as
2092 "[:alpha:]", are supported, and '-' has no special meaning).
2094 The characters asterisk (*) and question-mark (?) have no special meaning.
2096 Here's an example that specifies 6 suffixes to skip (since 1 of the 5 rules
2097 matches 2 suffixes):
2099 verb( --skip-compress=gz/jpg/mp[34]/7z/bz2)
2101 The default list of suffixes that will not be compressed is this (in this
2137 This list will be replaced by your bf(--skip-compress) list in all but one
2138 situation: a copy from a daemon rsync will add your skipped suffixes to
2139 its list of non-compressing files (and its list may be configured to a
2142 dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
2143 and user IDs rather than using user and group names and mapping them
2146 By default rsync will use the username and groupname to determine
2147 what ownership to give files. The special uid 0 and the special group
2148 0 are never mapped via user/group names even if the bf(--numeric-ids)
2149 option is not specified.
2151 If a user or group has no name on the source system or it has no match
2152 on the destination system, then the numeric ID
2153 from the source system is used instead. See also the comments on the
2154 "use chroot" setting in the rsyncd.conf manpage for information on how
2155 the chroot setting affects rsync's ability to look up the names of the
2156 users and groups and what you can do about it.
2158 dit(bf(--usermap=STRING, --groupmap=STRING)) These options allow you to
2159 specify users and groups that should be mapped to other values by the
2160 receiving side. The bf(STRING) is one or more bf(FROM):bf(TO) pairs of
2161 values separated by commas. Any matching bf(FROM) value from the sender is
2162 replaced with a bf(TO) value from the receiver. You may specify usernames
2163 or user IDs for the bf(FROM) and bf(TO) values, and the bf(FROM) value may
2164 also be a wild-card string, which will be matched against the sender's
2165 names (wild-cards do NOT match against ID numbers, though see below for
2166 why a '*' matches everything). You may instead specify a range of ID
2167 numbers via an inclusive range: LOW-HIGH. For example:
2169 verb( --usermap=0-99:nobody,wayne:admin,*:normal --groupmap=usr:1,1:usr)
2171 The first match in the list is the one that is used. You should specify
2172 all your user mappings using a single bf(--usermap) option, and/or all
2173 your group mappings using a single bf(--groupmap) option.
2175 Note that the sender's name for the 0 user and group are not transmitted
2176 to the receiver, so you should either match these values using a 0, or use
2177 the names in effect on the receiving side (typically "root"). All other
2178 bf(FROM) names match those in use on the sending side. All bf(TO) names
2179 match those in use on the receiving side.
2181 Any IDs that do not have a name on the sending side are treated as having an
2182 empty name for the purpose of matching. This allows them to be matched via
2183 a "*" or using an empty name. For instance:
2185 verb( --usermap=:nobody --groupmap=*:nobody)
2187 When the bf(--numeric-ids) option is used, the sender does not send any
2188 names, so all the IDs are treated as having an empty name. This means that
2189 you will need to specify numeric bf(FROM) values if you want to map these
2190 nameless IDs to different values.
2192 For the bf(--usermap) option to have any effect, the bf(-o) (bf(--owner))
2193 option must be used (or implied), and the receiver will need to be running
2194 as a super-user (see also the bf(--fake-super) option). For the bf(--groupmap)
2195 option to have any effect, the bf(-g) (bf(--groups)) option must be used
2196 (or implied), and the receiver will need to have permissions to set that
2199 dit(bf(--chown=USER:GROUP)) This option forces all files to be owned by USER
2200 with group GROUP. This is a simpler interface than using bf(--usermap) and
2201 bf(--groupmap) directly, but it is implemented using those options internally,
2202 so you cannot mix them. If either the USER or GROUP is empty, no mapping for
2203 the omitted user/group will occur. If GROUP is empty, the trailing colon may
2204 be omitted, but if USER is empty, a leading colon must be supplied.
2206 If you specify "--chown=foo:bar, this is exactly the same as specifying
2207 "--usermap=*:foo --groupmap=*:bar", only easier.
2209 dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum I/O
2210 timeout in seconds. If no data is transferred for the specified time
2211 then rsync will exit. The default is 0, which means no timeout.
2213 dit(bf(--contimeout)) This option allows you to set the amount of time
2214 that rsync will wait for its connection to an rsync daemon to succeed.
2215 If the timeout is reached, rsync exits with an error.
2217 dit(bf(--address)) By default rsync will bind to the wildcard address when
2218 connecting to an rsync daemon. The bf(--address) option allows you to
2219 specify a specific IP address (or hostname) to bind to. See also this
2220 option in the bf(--daemon) mode section.
2222 dit(bf(--port=PORT)) This specifies an alternate TCP port number to use
2223 rather than the default of 873. This is only needed if you are using the
2224 double-colon (::) syntax to connect with an rsync daemon (since the URL
2225 syntax has a way to specify the port as a part of the URL). See also this
2226 option in the bf(--daemon) mode section.
2228 dit(bf(--sockopts)) This option can provide endless fun for people
2229 who like to tune their systems to the utmost degree. You can set all
2230 sorts of socket options which may make transfers faster (or
2231 slower!). Read the man page for the code(setsockopt()) system call for
2232 details on some of the options you may be able to set. By default no
2233 special socket options are set. This only affects direct socket
2234 connections to a remote rsync daemon. This option also exists in the
2235 bf(--daemon) mode section.
2237 dit(bf(--blocking-io)) This tells rsync to use blocking I/O when launching
2238 a remote shell transport. If the remote shell is either rsh or remsh,
2239 rsync defaults to using
2240 blocking I/O, otherwise it defaults to using non-blocking I/O. (Note that
2241 ssh prefers non-blocking I/O.)
2243 dit(bf(--outbuf=MODE)) This sets the output buffering mode. The mode can be
2244 None (aka Unbuffered), Line, or Block (aka Full). You may specify as little
2245 as a single letter for the mode, and use upper or lower case.
2247 The main use of this option is to change Full buffering to Line buffering
2248 when rsync's output is going to a file or pipe.
2250 dit(bf(-i, --itemize-changes)) Requests a simple itemized list of the
2251 changes that are being made to each file, including attribute changes.
2252 This is exactly the same as specifying bf(--out-format='%i %n%L').
2253 If you repeat the option, unchanged files will also be output, but only
2254 if the receiving rsync is at least version 2.6.7 (you can use bf(-vv)
2255 with older versions of rsync, but that also turns on the output of other
2258 The "%i" escape has a cryptic output that is 11 letters long. The general
2259 format is like the string bf(YXcstpoguax), where bf(Y) is replaced by the
2260 type of update being done, bf(X) is replaced by the file-type, and the
2261 other letters represent attributes that may be output if they are being
2264 The update types that replace the bf(Y) are as follows:
2267 it() A bf(<) means that a file is being transferred to the remote host
2269 it() A bf(>) means that a file is being transferred to the local host
2271 it() A bf(c) means that a local change/creation is occurring for the item
2272 (such as the creation of a directory or the changing of a symlink, etc.).
2273 it() A bf(h) means that the item is a hard link to another item (requires
2275 it() A bf(.) means that the item is not being updated (though it might
2276 have attributes that are being modified).
2277 it() A bf(*) means that the rest of the itemized-output area contains
2278 a message (e.g. "deleting").
2281 The file-types that replace the bf(X) are: bf(f) for a file, a bf(d) for a
2282 directory, an bf(L) for a symlink, a bf(D) for a device, and a bf(S) for a
2283 special file (e.g. named sockets and fifos).
2285 The other letters in the string above are the actual letters that
2286 will be output if the associated attribute for the item is being updated or
2287 a "." for no change. Three exceptions to this are: (1) a newly created
2288 item replaces each letter with a "+", (2) an identical item replaces the
2289 dots with spaces, and (3) an unknown attribute replaces each letter with
2290 a "?" (this can happen when talking to an older rsync).
2292 The attribute that is associated with each letter is as follows:
2295 it() A bf(c) means either that a regular file has a different checksum
2296 (requires bf(--checksum)) or that a symlink, device, or special file has
2298 Note that if you are sending files to an rsync prior to 3.0.1, this
2299 change flag will be present only for checksum-differing regular files.
2300 it() A bf(s) means the size of a regular file is different and will be updated
2301 by the file transfer.
2302 it() A bf(t) means the modification time is different and is being updated
2303 to the sender's value (requires bf(--times)). An alternate value of bf(T)
2304 means that the modification time will be set to the transfer time, which happens
2305 when a file/symlink/device is updated without bf(--times) and when a
2306 symlink is changed and the receiver can't set its time.
2307 (Note: when using an rsync 3.0.0 client, you might see the bf(s) flag combined
2308 with bf(t) instead of the proper bf(T) flag for this time-setting failure.)
2309 it() A bf(p) means the permissions are different and are being updated to
2310 the sender's value (requires bf(--perms)).
2311 it() An bf(o) means the owner is different and is being updated to the
2312 sender's value (requires bf(--owner) and super-user privileges).
2313 it() A bf(g) means the group is different and is being updated to the
2314 sender's value (requires bf(--group) and the authority to set the group).
2315 it() A bf(u) means the access (use) time is different and is being updated to
2316 the sender's value (requires bf(--atimes)). An alternate value of bf(U)
2317 means that the access time will be set to the transfer time, which happens
2318 when a symlink or directory is updated.
2319 it() The bf(a) means that the ACL information changed.
2320 it() The bf(x) means that the extended attribute information changed.
2323 One other output is possible: when deleting files, the "%i" will output
2324 the string "*deleting" for each item that is being removed (assuming that
2325 you are talking to a recent enough rsync that it logs deletions instead of
2326 outputting them as a verbose message).
2328 dit(bf(--out-format=FORMAT)) This allows you to specify exactly what the
2329 rsync client outputs to the user on a per-update basis. The format is a
2330 text string containing embedded single-character escape sequences prefixed
2331 with a percent (%) character. A default format of "%n%L" is assumed if
2332 either bf(--info=name) or bf(-v) is specified (this tells you just the name
2333 of the file and, if the item is a link, where it points). For a full list
2334 of the possible escape characters, see the "log format" setting in the
2335 rsyncd.conf manpage.
2337 Specifying the bf(--out-format) option implies the bf(--info=name) option,
2338 which will mention each file, dir, etc. that gets updated in a significant
2339 way (a transferred file, a recreated symlink/device, or a touched
2340 directory). In addition, if the itemize-changes escape (%i) is included in
2341 the string (e.g. if the bf(--itemize-changes) option was used), the logging
2342 of names increases to mention any item that is changed in any way (as long
2343 as the receiving side is at least 2.6.4). See the bf(--itemize-changes)
2344 option for a description of the output of "%i".
2346 Rsync will output the out-format string prior to a file's transfer unless
2347 one of the transfer-statistic escapes is requested, in which case the
2348 logging is done at the end of the file's transfer. When this late logging
2349 is in effect and bf(--progress) is also specified, rsync will also output
2350 the name of the file being transferred prior to its progress information
2351 (followed, of course, by the out-format output).
2353 dit(bf(--log-file=FILE)) This option causes rsync to log what it is doing
2354 to a file. This is similar to the logging that a daemon does, but can be
2355 requested for the client side and/or the server side of a non-daemon
2356 transfer. If specified as a client option, transfer logging will be
2357 enabled with a default format of "%i %n%L". See the bf(--log-file-format)
2358 option if you wish to override this.
2360 Here's a example command that requests the remote side to log what is
2363 verb( rsync -av --remote-option=--log-file=/tmp/rlog src/ dest/)
2365 This is very useful if you need to debug why a connection is closing
2368 dit(bf(--log-file-format=FORMAT)) This allows you to specify exactly what
2369 per-update logging is put into the file specified by the bf(--log-file) option
2370 (which must also be specified for this option to have any effect). If you
2371 specify an empty string, updated files will not be mentioned in the log file.
2372 For a list of the possible escape characters, see the "log format" setting
2373 in the rsyncd.conf manpage.
2375 The default FORMAT used if bf(--log-file) is specified and this option is not
2378 dit(bf(--stats)) This tells rsync to print a verbose set of statistics
2379 on the file transfer, allowing you to tell how effective rsync's delta-transfer
2380 algorithm is for your data. This option is equivalent to bf(--info=stats2)
2381 if combined with 0 or 1 bf(-v) options, or bf(--info=stats3) if combined
2382 with 2 or more bf(-v) options.
2384 The current statistics are as follows: quote(itemization(
2385 it() bf(Number of files) is the count of all "files" (in the generic
2386 sense), which includes directories, symlinks, etc. The total count will
2387 be followed by a list of counts by filetype (if the total is non-zero).
2388 For example: "(reg: 5, dir: 3, link: 2, dev: 1, special: 1)" lists the
2389 totals for regular files, directories, symlinks, devices, and special
2390 files. If any of value is 0, it is completely omitted from the list.
2391 it() bf(Number of created files) is the count of how many "files" (generic
2392 sense) were created (as opposed to updated). The total count will be
2393 followed by a list of counts by filetype (if the total is non-zero).
2394 it() bf(Number of deleted files) is the count of how many "files" (generic
2395 sense) were created (as opposed to updated). The total count will be
2396 followed by a list of counts by filetype (if the total is non-zero).
2397 Note that this line is only output if deletions are in effect, and only
2398 if protocol 31 is being used (the default for rsync 3.1.x).
2399 it() bf(Number of regular files transferred) is the count of normal files
2400 that were updated via rsync's delta-transfer algorithm, which does not
2401 include dirs, symlinks, etc. Note that rsync 3.1.0 added the word
2402 "regular" into this heading.
2403 it() bf(Total file size) is the total sum of all file sizes in the transfer.
2404 This does not count any size for directories or special files, but does
2405 include the size of symlinks.
2406 it() bf(Total transferred file size) is the total sum of all files sizes
2407 for just the transferred files.
2408 it() bf(Literal data) is how much unmatched file-update data we had to
2409 send to the receiver for it to recreate the updated files.
2410 it() bf(Matched data) is how much data the receiver got locally when
2411 recreating the updated files.
2412 it() bf(File list size) is how big the file-list data was when the sender
2413 sent it to the receiver. This is smaller than the in-memory size for the
2414 file list due to some compressing of duplicated data when rsync sends the
2416 it() bf(File list generation time) is the number of seconds that the
2417 sender spent creating the file list. This requires a modern rsync on the
2418 sending side for this to be present.
2419 it() bf(File list transfer time) is the number of seconds that the sender
2420 spent sending the file list to the receiver.
2421 it() bf(Total bytes sent) is the count of all the bytes that rsync sent
2422 from the client side to the server side.
2423 it() bf(Total bytes received) is the count of all non-message bytes that
2424 rsync received by the client side from the server side. "Non-message"
2425 bytes means that we don't count the bytes for a verbose message that the
2426 server sent to us, which makes the stats more consistent.
2429 dit(bf(-8, --8-bit-output)) This tells rsync to leave all high-bit characters
2430 unescaped in the output instead of trying to test them to see if they're
2431 valid in the current locale and escaping the invalid ones. All control
2432 characters (but never tabs) are always escaped, regardless of this option's
2435 The escape idiom that started in 2.6.7 is to output a literal backslash (\)
2436 and a hash (#), followed by exactly 3 octal digits. For example, a newline
2437 would output as "\#012". A literal backslash that is in a filename is not
2438 escaped unless it is followed by a hash and 3 digits (0-9).
2443 dit(bf(-h, --human-readable)) Output numbers in a more human-readable format.
2444 There are 3 possible levels: (1) output numbers with a separator between each
2445 set of 3 digits (either a comma or a period, depending on if the decimal point
2446 is represented by a period or a comma); (2) output numbers in units of 1000
2447 (with a character suffix for larger units -- see below); (3) output numbers in
2450 The default is human-readable level 1. Each bf(-h) option increases the level
2451 by one. You can take the level down to 0 (to output numbers as pure digits) by
2452 specifying the bf(--no-human-readable) (bf(--no-h)) option.
2454 The unit letters that are appended in levels 2 and 3 are: K (kilo), M (mega),
2455 G (giga), or T (tera). For example, a 1234567-byte file would output as 1.23M
2456 in level-2 (assuming that a period is your local decimal point).
2458 Backward compatibility note: versions of rsync prior to 3.1.0 do not support
2459 human-readable level 1, and they default to level 0. Thus, specifying one or
2460 two bf(-h) options will behave in a comparable manner in old and new versions
2461 as long as you didn't specify a bf(--no-h) option prior to one or more bf(-h)
2462 options. See the bf(--list-only) option for one difference.
2464 dit(bf(--partial)) By default, rsync will delete any partially
2465 transferred file if the transfer is interrupted. In some circumstances
2466 it is more desirable to keep partially transferred files. Using the
2467 bf(--partial) option tells rsync to keep the partial file which should
2468 make a subsequent transfer of the rest of the file much faster.
2470 dit(bf(--partial-dir=DIR)) A better way to keep partial files than the
2471 bf(--partial) option is to specify a em(DIR) that will be used to hold the
2472 partial data (instead of writing it out to the destination file).
2473 On the next transfer, rsync will use a file found in this
2474 dir as data to speed up the resumption of the transfer and then delete it
2475 after it has served its purpose.
2477 Note that if bf(--whole-file) is specified (or implied), any partial-dir
2478 file that is found for a file that is being updated will simply be removed
2480 rsync is sending files without using rsync's delta-transfer algorithm).
2482 Rsync will create the em(DIR) if it is missing (just the last dir -- not
2483 the whole path). This makes it easy to use a relative path (such as
2484 "bf(--partial-dir=.rsync-partial)") to have rsync create the
2485 partial-directory in the destination file's directory when needed, and then
2486 remove it again when the partial file is deleted. Note that the directory
2487 is only removed if it is a relative pathname, as it is expected that an
2488 absolute path is to a directory that is reserved for partial-dir work.
2490 If the partial-dir value is not an absolute path, rsync will add an exclude
2491 rule at the end of all your existing excludes. This will prevent the
2492 sending of any partial-dir files that may exist on the sending side, and
2493 will also prevent the untimely deletion of partial-dir items on the
2494 receiving side. An example: the above bf(--partial-dir) option would add
2495 the equivalent of "bf(-f '-p .rsync-partial/')" at the end of any other
2498 If you are supplying your own exclude rules, you may need to add your own
2499 exclude/hide/protect rule for the partial-dir because (1) the auto-added
2500 rule may be ineffective at the end of your other rules, or (2) you may wish
2501 to override rsync's exclude choice. For instance, if you want to make
2502 rsync clean-up any left-over partial-dirs that may be lying around, you
2503 should specify bf(--delete-after) and add a "risk" filter rule, e.g.
2504 bf(-f 'R .rsync-partial/'). (Avoid using bf(--delete-before) or
2505 bf(--delete-during) unless you don't need rsync to use any of the
2506 left-over partial-dir data during the current run.)
2508 IMPORTANT: the bf(--partial-dir) should not be writable by other users or it
2509 is a security risk. E.g. AVOID "/tmp".
2511 You can also set the partial-dir value the RSYNC_PARTIAL_DIR environment
2512 variable. Setting this in the environment does not force bf(--partial) to be
2513 enabled, but rather it affects where partial files go when bf(--partial) is
2514 specified. For instance, instead of using bf(--partial-dir=.rsync-tmp)
2515 along with bf(--progress), you could set RSYNC_PARTIAL_DIR=.rsync-tmp in your
2516 environment and then just use the bf(-P) option to turn on the use of the
2517 .rsync-tmp dir for partial transfers. The only times that the bf(--partial)
2518 option does not look for this environment value are (1) when bf(--inplace) was
2519 specified (since bf(--inplace) conflicts with bf(--partial-dir)), and (2) when
2520 bf(--delay-updates) was specified (see below).
2522 When a modern rsync resumes the transfer of a file in the partial-dir, that
2523 partial file is now updated in-place instead of creating yet another tmp-file
2524 copy (so it maxes out at dest + tmp instead of dest + partial + tmp). This
2525 requires both ends of the transfer to be at least version 3.2.0.
2527 For the purposes of the daemon-config's "refuse options" setting,
2528 bf(--partial-dir) does em(not) imply bf(--partial). This is so that a
2529 refusal of the bf(--partial) option can be used to disallow the overwriting
2530 of destination files with a partial transfer, while still allowing the
2531 safer idiom provided by bf(--partial-dir).
2533 dit(bf(--delay-updates)) This option puts the temporary file from each
2534 updated file into a holding directory until the end of the
2535 transfer, at which time all the files are renamed into place in rapid
2536 succession. This attempts to make the updating of the files a little more
2537 atomic. By default the files are placed into a directory named ".~tmp~" in
2538 each file's destination directory, but if you've specified the
2539 bf(--partial-dir) option, that directory will be used instead. See the
2540 comments in the bf(--partial-dir) section for a discussion of how this
2541 ".~tmp~" dir will be excluded from the transfer, and what you can do if
2542 you want rsync to cleanup old ".~tmp~" dirs that might be lying around.
2543 Conflicts with bf(--inplace) and bf(--append).
2545 This option uses more memory on the receiving side (one bit per file
2546 transferred) and also requires enough free disk space on the receiving
2547 side to hold an additional copy of all the updated files. Note also that
2548 you should not use an absolute path to bf(--partial-dir) unless (1)
2550 chance of any of the files in the transfer having the same name (since all
2551 the updated files will be put into a single directory if the path is
2553 and (2) there are no mount points in the hierarchy (since the
2554 delayed updates will fail if they can't be renamed into place).
2556 See also the "atomic-rsync" perl script in the "support" subdir for an
2557 update algorithm that is even more atomic (it uses bf(--link-dest) and a
2558 parallel hierarchy of files).
2560 dit(bf(-m, --prune-empty-dirs)) This option tells the receiving rsync to get
2561 rid of empty directories from the file-list, including nested directories
2562 that have no non-directory children. This is useful for avoiding the
2563 creation of a bunch of useless directories when the sending rsync is
2564 recursively scanning a hierarchy of files using include/exclude/filter
2567 Note that the use of transfer rules, such as the bf(--min-size) option, does
2568 not affect what goes into the file list, and thus does not leave directories
2569 empty, even if none of the files in a directory match the transfer rule.
2571 Because the file-list is actually being pruned, this option also affects
2572 what directories get deleted when a delete is active. However, keep in
2573 mind that excluded files and directories can prevent existing items from
2574 being deleted due to an exclude both hiding source files and protecting
2575 destination files. See the perishable filter-rule option for how to avoid
2578 You can prevent the pruning of certain empty directories from the file-list
2579 by using a global "protect" filter. For instance, this option would ensure
2580 that the directory "emptydir" was kept in the file-list:
2582 quote( --filter 'protect emptydir/')
2584 Here's an example that copies all .pdf files in a hierarchy, only creating
2585 the necessary destination directories to hold the .pdf files, and ensures
2586 that any superfluous files and directories in the destination are removed
2587 (note the hide filter of non-directories being used instead of an exclude):
2589 quote( rsync -avm --del --include='*.pdf' -f 'hide,! */' src/ dest)
2591 If you didn't want to remove superfluous destination files, the more
2592 time-honored options of "bf(--include='*/' --exclude='*')" would work fine
2593 in place of the hide-filter (if that is more natural to you).
2595 dit(bf(--progress)) This option tells rsync to print information
2596 showing the progress of the transfer. This gives a bored user
2598 With a modern rsync this is the same as specifying
2599 bf(--info=flist2,name,progress), but any user-supplied settings for those
2600 info flags takes precedence (e.g. "--info=flist0 --progress").
2602 While rsync is transferring a regular file, it updates a progress line that
2605 verb( 782448 63% 110.64kB/s 0:00:04)
2607 In this example, the receiver has reconstructed 782448 bytes or 63% of the
2608 sender's file, which is being reconstructed at a rate of 110.64 kilobytes
2609 per second, and the transfer will finish in 4 seconds if the current rate
2610 is maintained until the end.
2612 These statistics can be misleading if rsync's delta-transfer algorithm is
2613 in use. For example, if the sender's file consists of the basis file
2614 followed by additional data, the reported rate will probably drop
2615 dramatically when the receiver gets to the literal data, and the transfer
2616 will probably take much longer to finish than the receiver estimated as it
2617 was finishing the matched part of the file.
2619 When the file transfer finishes, rsync replaces the progress line with a
2620 summary line that looks like this:
2622 verb( 1,238,099 100% 146.38kB/s 0:00:08 (xfr#5, to-chk=169/396))
2624 In this example, the file was 1,238,099 bytes long in total, the average rate
2625 of transfer for the whole file was 146.38 kilobytes per second over the 8
2626 seconds that it took to complete, it was the 5th transfer of a regular file
2627 during the current rsync session, and there are 169 more files for the
2628 receiver to check (to see if they are up-to-date or not) remaining out of
2629 the 396 total files in the file-list.
2631 In an incremental recursion scan, rsync won't know the total number of files
2632 in the file-list until it reaches the ends of the scan, but since it starts to
2633 transfer files during the scan, it will display a line with the text "ir-chk"
2634 (for incremental recursion check) instead of "to-chk" until the point that it
2635 knows the full size of the list, at which point it will switch to using
2636 "to-chk". Thus, seeing "ir-chk" lets you know that the total count of files
2637 in the file list is still going to increase (and each time it does, the count
2638 of files left to check will increase by the number of the files added to the
2641 dit(bf(-P)) The bf(-P) option is equivalent to bf(--partial) bf(--progress). Its
2642 purpose is to make it much easier to specify these two options for a long
2643 transfer that may be interrupted.
2645 There is also a bf(--info=progress2) option that outputs statistics based
2646 on the whole transfer, rather than individual files. Use this flag without
2647 outputting a filename (e.g. avoid bf(-v) or specify bf(--info=name0)) if you
2648 want to see how the transfer is doing without scrolling the screen with a
2649 lot of names. (You don't need to specify the bf(--progress) option in
2650 order to use bf(--info=progress2).)
2652 Finally, you can get an instant progress report by sending rsync a signal of
2653 either SIGINFO or SIGVTALRM. On BSD systems, a SIGINFO is generated by typing a
2654 Ctrl+T (Linux doesn't currently support a SIGINFO signal). When the client-side
2655 process receives one of those signals, it sets a flag to output a single
2656 progress report which is output when the current file transfer finishes (so it
2657 may take a little time if a big file is being handled when the signal arrives).
2658 A filename is output (if needed) followed by the --info=progress2 format of
2659 progress info. If you don't know which of the 3 rsync processes is the client
2660 process, it's OK to signal all of them (since the non-client processes ignore
2663 CAUTION: sending SIGVTALRM to an older rsync (pre-3.2.0) will kill it.
2665 dit(bf(--password-file=FILE)) This option allows you to provide a password for
2666 accessing an rsync daemon via a file or via standard input if bf(FILE) is
2667 bf(-). The file should contain just the password on the first line (all other
2668 lines are ignored). Rsync will exit with an error if bf(FILE) is world
2669 readable or if a root-run rsync command finds a non-root-owned file.
2671 This option does not supply a password to a remote shell transport such as
2672 ssh; to learn how to do that, consult the remote shell's documentation.
2673 When accessing an rsync daemon using a remote shell as the transport, this
2674 option only comes into effect after the remote shell finishes its
2675 authentication (i.e. if you have also specified a password in the daemon's
2678 dit(bf(--list-only)) This option will cause the source files to be listed
2679 instead of transferred. This option is inferred if there is a single source
2680 arg and no destination specified, so its main uses are: (1) to turn a copy
2681 command that includes a
2682 destination arg into a file-listing command, or (2) to be able to specify
2683 more than one source arg (note: be sure to include the destination).
2684 Caution: keep in mind that a source arg with a wild-card is expanded by the
2685 shell into multiple args, so it is never safe to try to list such an arg
2686 without using this option. For example:
2688 verb( rsync -av --list-only foo* dest/)
2690 Starting with rsync 3.1.0, the sizes output by bf(--list-only) are affected
2691 by the bf(--human-readable) option. By default they will contain digit
2692 separators, but higher levels of readability will output the sizes with
2693 unit suffixes. Note also that the column width for the size output has
2694 increased from 11 to 14 characters for all human-readable levels. Use
2695 bf(--no-h) if you want just digits in the sizes, and the old column width
2698 Compatibility note: when requesting a remote listing of files from an rsync
2699 that is version 2.6.3 or older, you may encounter an error if you ask for a
2700 non-recursive listing. This is because a file listing implies the bf(--dirs)
2701 option w/o bf(--recursive), and older rsyncs don't have that option. To
2702 avoid this problem, either specify the bf(--no-dirs) option (if you don't
2703 need to expand a directory's content), or turn on recursion and exclude
2704 the content of subdirectories: bf(-r --exclude='/*/*').
2706 dit(bf(--bwlimit=RATE)) This option allows you to specify the maximum transfer
2707 rate for the data sent over the socket, specified in units per second. The
2708 RATE value can be suffixed with a string to indicate a size multiplier, and may
2709 be a fractional value (e.g. "bf(--bwlimit=1.5m)"). If no suffix is specified,
2710 the value will be assumed to be in units of 1024 bytes (as if "K" or "KiB" had
2711 been appended). See the bf(--max-size) option for a description of all the
2712 available suffixes. A value of zero specifies no limit.
2714 For backward-compatibility reasons, the rate limit will be rounded to the
2715 nearest KiB unit, so no rate smaller than 1024 bytes per second is possible.
2717 Rsync writes data over the socket in blocks, and this option both limits the
2718 size of the blocks that rsync writes, and tries to keep the average transfer
2719 rate at the requested limit. Some "burstiness" may be seen where rsync writes
2720 out a block of data and then sleeps to bring the average rate into compliance.
2722 Due to the internal buffering of data, the bf(--progress) option may not be an
2723 accurate reflection on how fast the data is being sent. This is because some
2724 files can show up as being rapidly sent when the data is quickly buffered,
2725 while other can show up as very slow when the flushing of the output buffer
2726 occurs. This may be fixed in a future version.
2728 dit(bf(--write-batch=FILE)) Record a file that can later be applied to
2729 another identical destination with bf(--read-batch). See the "BATCH MODE"
2730 section for details, and also the bf(--only-write-batch) option.
2732 dit(bf(--only-write-batch=FILE)) Works like bf(--write-batch), except that
2733 no updates are made on the destination system when creating the batch.
2734 This lets you transport the changes to the destination system via some
2735 other means and then apply the changes via bf(--read-batch).
2737 Note that you can feel free to write the batch directly to some portable
2738 media: if this media fills to capacity before the end of the transfer, you
2739 can just apply that partial transfer to the destination and repeat the
2740 whole process to get the rest of the changes (as long as you don't mind a
2741 partially updated destination system while the multi-update cycle is
2744 Also note that you only save bandwidth when pushing changes to a remote
2745 system because this allows the batched data to be diverted from the sender
2746 into the batch file without having to flow over the wire to the receiver
2747 (when pulling, the sender is remote, and thus can't write the batch).
2749 dit(bf(--read-batch=FILE)) Apply all of the changes stored in FILE, a
2750 file previously generated by bf(--write-batch).
2751 If em(FILE) is bf(-), the batch data will be read from standard input.
2752 See the "BATCH MODE" section for details.
2757 dit(bf(--protocol=NUM)) Force an older protocol version to be used. This
2758 is useful for creating a batch file that is compatible with an older
2759 version of rsync. For instance, if rsync 2.6.4 is being used with the
2760 bf(--write-batch) option, but rsync 2.6.3 is what will be used to run the
2761 bf(--read-batch) option, you should use "--protocol=28" when creating the
2762 batch file to force the older protocol version to be used in the batch
2763 file (assuming you can't upgrade the rsync on the reading system).
2765 dit(bf(--iconv=CONVERT_SPEC)) Rsync can convert filenames between character
2766 sets using this option. Using a CONVERT_SPEC of "." tells rsync to look up
2767 the default character-set via the locale setting. Alternately, you can
2768 fully specify what conversion to do by giving a local and a remote charset
2769 separated by a comma in the order bf(--iconv=LOCAL,REMOTE), e.g.
2770 bf(--iconv=utf8,iso88591). This order ensures that the option
2771 will stay the same whether you're pushing or pulling files.
2772 Finally, you can specify either bf(--no-iconv) or a CONVERT_SPEC of "-"
2773 to turn off any conversion.
2774 The default setting of this option is site-specific, and can also be
2775 affected via the RSYNC_ICONV environment variable.
2777 For a list of what charset names your local iconv library supports, you can
2780 If you specify the bf(--protect-args) option (bf(-s)), rsync will translate
2781 the filenames you specify on the command-line that are being sent to the
2782 remote host. See also the bf(--files-from) option.
2784 Note that rsync does not do any conversion of names in filter files
2785 (including include/exclude files). It is up to you to ensure that you're
2786 specifying matching rules that can match on both sides of the transfer.
2787 For instance, you can specify extra include/exclude rules if there are
2788 filename differences on the two sides that need to be accounted for.
2790 When you pass an bf(--iconv) option to an rsync daemon that allows it, the
2791 daemon uses the charset specified in its "charset" configuration parameter
2792 regardless of the remote charset you actually pass. Thus, you may feel free to
2793 specify just the local charset for a daemon transfer (e.g. bf(--iconv=utf8)).
2795 dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6
2796 when creating sockets. This only affects sockets that rsync has direct
2797 control over, such as the outgoing socket when directly contacting an
2798 rsync daemon. See also these options in the bf(--daemon) mode section.
2800 If rsync was complied without support for IPv6, the bf(--ipv6) option
2801 will have no effect. The bf(--version) output will tell you if this
2804 dit(bf(--checksum-seed=NUM)) Set the checksum seed to the integer NUM. This 4
2805 byte checksum seed is included in each block and MD4 file checksum calculation
2806 (the more modern MD5 file checksums don't use a seed). By default the checksum
2807 seed is generated by the server and defaults to the current code(time()). This
2808 option is used to set a specific checksum seed, which is useful for
2809 applications that want repeatable block checksums, or in the case where the
2810 user wants a more random checksum seed. Setting NUM to 0 causes rsync to use
2811 the default of code(time()) for checksum seed.
2815 manpagesection(DAEMON OPTIONS)
2817 The options allowed when starting an rsync daemon are as follows:
2821 dit(bf(--daemon)) This tells rsync that it is to run as a daemon. The
2822 daemon you start running may be accessed using an rsync client using
2823 the bf(host::module) or bf(rsync://host/module/) syntax.
2825 If standard input is a socket then rsync will assume that it is being
2826 run via inetd, otherwise it will detach from the current terminal and
2827 become a background daemon. The daemon will read the config file
2828 (rsyncd.conf) on each connect made by a client and respond to
2829 requests accordingly. See the bf(rsyncd.conf)(5) man page for more
2832 dit(bf(--address)) By default rsync will bind to the wildcard address when
2833 run as a daemon with the bf(--daemon) option. The bf(--address) option
2834 allows you to specify a specific IP address (or hostname) to bind to. This
2835 makes virtual hosting possible in conjunction with the bf(--config) option.
2836 See also the "address" global option in the rsyncd.conf manpage.
2838 dit(bf(--bwlimit=RATE)) This option allows you to specify the maximum transfer
2839 rate for the data the daemon sends over the socket. The client can still
2840 specify a smaller bf(--bwlimit) value, but no larger value will be allowed.
2841 See the client version of this option (above) for some extra details.
2843 dit(bf(--config=FILE)) This specifies an alternate config file than
2844 the default. This is only relevant when bf(--daemon) is specified.
2845 The default is /etc/rsyncd.conf unless the daemon is running over
2846 a remote shell program and the remote user is not the super-user; in that case
2847 the default is rsyncd.conf in the current directory (typically $HOME).
2849 dit(bf(-M, --dparam=OVERRIDE)) This option can be used to set a daemon-config
2850 parameter when starting up rsync in daemon mode. It is equivalent to adding
2851 the parameter at the end of the global settings prior to the first module's
2852 definition. The parameter names can be specified without spaces, if you so
2853 desire. For instance:
2855 verb( rsync --daemon -M pidfile=/path/rsync.pid )
2857 dit(bf(--no-detach)) When running as a daemon, this option instructs
2858 rsync to not detach itself and become a background process. This
2859 option is required when running as a service on Cygwin, and may also
2860 be useful when rsync is supervised by a program such as
2861 bf(daemontools) or AIX's bf(System Resource Controller).
2862 bf(--no-detach) is also recommended when rsync is run under a
2863 debugger. This option has no effect if rsync is run from inetd or
2866 dit(bf(--port=PORT)) This specifies an alternate TCP port number for the
2867 daemon to listen on rather than the default of 873. See also the "port"
2868 global option in the rsyncd.conf manpage.
2870 dit(bf(--log-file=FILE)) This option tells the rsync daemon to use the
2871 given log-file name instead of using the "log file" setting in the config
2874 dit(bf(--log-file-format=FORMAT)) This option tells the rsync daemon to use the
2875 given FORMAT string instead of using the "log format" setting in the config
2876 file. It also enables "transfer logging" unless the string is empty, in which
2877 case transfer logging is turned off.
2879 dit(bf(--sockopts)) This overrides the bf(socket options) setting in the
2880 rsyncd.conf file and has the same syntax.
2882 dit(bf(-v, --verbose)) This option increases the amount of information the
2883 daemon logs during its startup phase. After the client connects, the
2884 daemon's verbosity level will be controlled by the options that the client
2885 used and the "max verbosity" setting in the module's config section.
2887 dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6
2888 when creating the incoming sockets that the rsync daemon will use to
2889 listen for connections. One of these options may be required in older
2890 versions of Linux to work around an IPv6 bug in the kernel (if you see
2891 an "address already in use" error when nothing else is using the port,
2892 try specifying bf(--ipv6) or bf(--ipv4) when starting the daemon).
2894 If rsync was complied without support for IPv6, the bf(--ipv6) option
2895 will have no effect. The bf(--version) output will tell you if this
2898 dit(bf(-h, --help)) When specified after bf(--daemon), print a short help
2899 page describing the options available for starting an rsync daemon.
2903 manpagesection(FILTER RULES)
2905 The filter rules allow for flexible selection of which files to transfer
2906 (include) and which files to skip (exclude). The rules either directly
2907 specify include/exclude patterns or they specify a way to acquire more
2908 include/exclude patterns (e.g. to read them from a file).
2910 As the list of files/directories to transfer is built, rsync checks each
2911 name to be transferred against the list of include/exclude patterns in
2912 turn, and the first matching pattern is acted on: if it is an exclude
2913 pattern, then that file is skipped; if it is an include pattern then that
2914 filename is not skipped; if no matching pattern is found, then the
2915 filename is not skipped.
2917 Rsync builds an ordered list of filter rules as specified on the
2918 command-line. Filter rules have the following syntax:
2921 tt(RULE [PATTERN_OR_FILENAME])nl()
2922 tt(RULE,MODIFIERS [PATTERN_OR_FILENAME])nl()
2925 You have your choice of using either short or long RULE names, as described
2926 below. If you use a short-named rule, the ',' separating the RULE from the
2927 MODIFIERS is optional. The PATTERN or FILENAME that follows (when present)
2928 must come after either a single space or an underscore (_).
2929 Here are the available rule prefixes:
2932 bf(exclude, -) specifies an exclude pattern. nl()
2933 bf(include, +) specifies an include pattern. nl()
2934 bf(merge, .) specifies a merge-file to read for more rules. nl()
2935 bf(dir-merge, :) specifies a per-directory merge-file. nl()
2936 bf(hide, H) specifies a pattern for hiding files from the transfer. nl()
2937 bf(show, S) files that match the pattern are not hidden. nl()
2938 bf(protect, P) specifies a pattern for protecting files from deletion. nl()
2939 bf(risk, R) files that match the pattern are not protected. nl()
2940 bf(clear, !) clears the current include/exclude list (takes no arg) nl()
2943 When rules are being read from a file, empty lines are ignored, as are
2944 comment lines that start with a "#".
2946 Note that the bf(--include)/bf(--exclude) command-line options do not allow the
2947 full range of rule parsing as described above -- they only allow the
2948 specification of include/exclude patterns plus a "!" token to clear the
2949 list (and the normal comment parsing when rules are read from a file).
2951 does not begin with "- " (dash, space) or "+ " (plus, space), then the
2952 rule will be interpreted as if "+ " (for an include option) or "- " (for
2953 an exclude option) were prefixed to the string. A bf(--filter) option, on
2954 the other hand, must always contain either a short or long rule name at the
2957 Note also that the bf(--filter), bf(--include), and bf(--exclude) options take one
2958 rule/pattern each. To add multiple ones, you can repeat the options on
2959 the command-line, use the merge-file syntax of the bf(--filter) option, or
2960 the bf(--include-from)/bf(--exclude-from) options.
2962 manpagesection(INCLUDE/EXCLUDE PATTERN RULES)
2964 You can include and exclude files by specifying patterns using the "+",
2965 "-", etc. filter rules (as introduced in the FILTER RULES section above).
2966 The include/exclude rules each specify a pattern that is matched against
2967 the names of the files that are going to be transferred. These patterns
2968 can take several forms:
2971 it() if the pattern starts with a / then it is anchored to a
2972 particular spot in the hierarchy of files, otherwise it is matched
2973 against the end of the pathname. This is similar to a leading ^ in
2974 regular expressions.
2975 Thus "/foo" would match a name of "foo" at either the "root of the
2976 transfer" (for a global rule) or in the merge-file's directory (for a
2977 per-directory rule).
2978 An unqualified "foo" would match a name of "foo" anywhere in the
2979 tree because the algorithm is applied recursively from the
2980 top down; it behaves as if each path component gets a turn at being the
2981 end of the filename. Even the unanchored "sub/foo" would match at
2982 any point in the hierarchy where a "foo" was found within a directory
2983 named "sub". See the section on ANCHORING INCLUDE/EXCLUDE PATTERNS for
2984 a full discussion of how to specify a pattern that matches at the root
2986 it() if the pattern ends with a / then it will only match a
2987 directory, not a regular file, symlink, or device.
2988 it() rsync chooses between doing a simple string match and wildcard
2989 matching by checking if the pattern contains one of these three wildcard
2990 characters: '*', '?', and '[' .
2991 it() a '*' matches any path component, but it stops at slashes.
2992 it() use '**' to match anything, including slashes.
2993 it() a '?' matches any character except a slash (/).
2994 it() a '[' introduces a character class, such as [a-z] or [[:alpha:]].
2995 it() in a wildcard pattern, a backslash can be used to escape a wildcard
2996 character, but it is matched literally when no wildcards are present.
2997 This means that there is an extra level of backslash removal when a
2998 pattern contains wildcard characters compared to a pattern that has none.
2999 e.g. if you add a wildcard to "foo\bar" (which matches the backslash) you
3000 would need to use "foo\\bar*" to avoid the "\b" becoming just "b".
3001 it() if the pattern contains a / (not counting a trailing /) or a "**",
3002 then it is matched against the full pathname, including any leading
3003 directories. If the pattern doesn't contain a / or a "**", then it is
3004 matched only against the final component of the filename.
3005 (Remember that the algorithm is applied recursively so "full filename"
3006 can actually be any portion of a path from the starting directory on
3008 it() a trailing "dir_name/***" will match both the directory (as if
3009 "dir_name/" had been specified) and everything in the directory
3010 (as if "dir_name/**" had been specified). This behavior was added in
3014 Note that, when using the bf(--recursive) (bf(-r)) option (which is implied by
3015 bf(-a)), every subdir component of every path is visited left to right, with
3016 each directory having a chance for exclusion before its content. In this way
3017 include/exclude patterns are applied recursively to the pathname of each node
3018 in the filesystem's tree (those inside the transfer). The exclude patterns
3019 short-circuit the directory traversal stage as rsync finds the files to send.
3021 For instance, to include "/foo/bar/baz", the directories "/foo" and "/foo/bar"
3022 must not be excluded. Excluding one of those parent directories prevents the
3023 examination of its content, cutting off rsync's recursion into those paths and
3024 rendering the include for "/foo/bar/baz" ineffectual (since rsync can't match
3025 something it never sees in the cut-off section of the directory hierarchy).
3027 The concept path exclusion is particularly important when using a trailing '*'
3028 rule. For instance, this won't work:
3031 tt(+ /some/path/this-file-will-not-be-found)nl()
3032 tt(+ /file-is-included)nl()
3036 This fails because the parent directory "some" is excluded by the '*'
3037 rule, so rsync never visits any of the files in the "some" or "some/path"
3038 directories. One solution is to ask for all directories in the hierarchy
3039 to be included by using a single rule: "+ */" (put it somewhere before the
3040 "- *" rule), and perhaps use the bf(--prune-empty-dirs) option. Another
3041 solution is to add specific include rules for all
3042 the parent dirs that need to be visited. For instance, this set of rules
3047 tt(+ /some/path/)nl()
3048 tt(+ /some/path/this-file-is-found)nl()
3049 tt(+ /file-also-included)nl()
3053 Here are some examples of exclude/include matching:
3056 it() "- *.o" would exclude all names matching *.o
3057 it() "- /foo" would exclude a file (or directory) named foo in the
3058 transfer-root directory
3059 it() "- foo/" would exclude any directory named foo
3060 it() "- /foo/*/bar" would exclude any file named bar which is at two
3061 levels below a directory named foo in the transfer-root directory
3062 it() "- /foo/**/bar" would exclude any file named bar two
3063 or more levels below a directory named foo in the transfer-root directory
3064 it() The combination of "+ */", "+ *.c", and "- *" would include all
3065 directories and C source files but nothing else (see also the
3066 bf(--prune-empty-dirs) option)
3067 it() The combination of "+ foo/", "+ foo/bar.c", and "- *" would include
3068 only the foo directory and foo/bar.c (the foo directory must be
3069 explicitly included or it would be excluded by the "*")
3072 The following modifiers are accepted after a "+" or "-":
3075 it() A bf(/) specifies that the include/exclude rule should be matched
3076 against the absolute pathname of the current item. For example,
3077 "-/ /etc/passwd" would exclude the passwd file any time the transfer
3078 was sending files from the "/etc" directory, and "-/ subdir/foo"
3079 would always exclude "foo" when it is in a dir named "subdir", even
3080 if "foo" is at the root of the current transfer.
3081 it() A bf(!) specifies that the include/exclude should take effect if
3082 the pattern fails to match. For instance, "-! */" would exclude all
3084 it() A bf(C) is used to indicate that all the global CVS-exclude rules
3085 should be inserted as excludes in place of the "-C". No arg should
3087 it() An bf(s) is used to indicate that the rule applies to the sending
3088 side. When a rule affects the sending side, it prevents files from
3089 being transferred. The default is for a rule to affect both sides
3090 unless bf(--delete-excluded) was specified, in which case default rules
3091 become sender-side only. See also the hide (H) and show (S) rules,
3092 which are an alternate way to specify sending-side includes/excludes.
3093 it() An bf(r) is used to indicate that the rule applies to the receiving
3094 side. When a rule affects the receiving side, it prevents files from
3095 being deleted. See the bf(s) modifier for more info. See also the
3096 protect (P) and risk (R) rules, which are an alternate way to
3097 specify receiver-side includes/excludes.
3098 it() A bf(p) indicates that a rule is perishable, meaning that it is
3099 ignored in directories that are being deleted. For instance, the bf(-C)
3100 option's default rules that exclude things like "CVS" and "*.o" are
3101 marked as perishable, and will not prevent a directory that was removed
3102 on the source from being deleted on the destination.
3103 it() An bf(x) indicates that a rule affects xattr names in xattr copy/delete
3104 operations (and is thus ignored when matching file/dir names). If no
3105 xattr-matching rules are specified, a default xattr filtering rule is
3106 used (see the bf(--xattrs) option).
3109 manpagesection(MERGE-FILE FILTER RULES)
3111 You can merge whole files into your filter rules by specifying either a
3112 merge (.) or a dir-merge (:) filter rule (as introduced in the FILTER RULES
3115 There are two kinds of merged files -- single-instance ('.') and
3116 per-directory (':'). A single-instance merge file is read one time, and
3117 its rules are incorporated into the filter list in the place of the "."
3118 rule. For per-directory merge files, rsync will scan every directory that
3119 it traverses for the named file, merging its contents when the file exists
3120 into the current list of inherited rules. These per-directory rule files
3121 must be created on the sending side because it is the sending side that is
3122 being scanned for the available files to transfer. These rule files may
3123 also need to be transferred to the receiving side if you want them to
3124 affect what files don't get deleted (see PER-DIRECTORY RULES AND DELETE
3130 tt(merge /etc/rsync/default.rules)nl()
3131 tt(. /etc/rsync/default.rules)nl()
3132 tt(dir-merge .per-dir-filter)nl()
3133 tt(dir-merge,n- .non-inherited-per-dir-excludes)nl()
3134 tt(:n- .non-inherited-per-dir-excludes)nl()
3137 The following modifiers are accepted after a merge or dir-merge rule:
3140 it() A bf(-) specifies that the file should consist of only exclude
3141 patterns, with no other rule-parsing except for in-file comments.
3142 it() A bf(+) specifies that the file should consist of only include
3143 patterns, with no other rule-parsing except for in-file comments.
3144 it() A bf(C) is a way to specify that the file should be read in a
3145 CVS-compatible manner. This turns on 'n', 'w', and '-', but also
3146 allows the list-clearing token (!) to be specified. If no filename is
3147 provided, ".cvsignore" is assumed.
3148 it() A bf(e) will exclude the merge-file name from the transfer; e.g.
3149 "dir-merge,e .rules" is like "dir-merge .rules" and "- .rules".
3150 it() An bf(n) specifies that the rules are not inherited by subdirectories.
3151 it() A bf(w) specifies that the rules are word-split on whitespace instead
3152 of the normal line-splitting. This also turns off comments. Note: the
3153 space that separates the prefix from the rule is treated specially, so
3154 "- foo + bar" is parsed as two rules (assuming that prefix-parsing wasn't
3156 it() You may also specify any of the modifiers for the "+" or "-" rules
3157 (above) in order to have the rules that are read in from the file
3158 default to having that modifier set (except for the bf(!) modifier, which
3159 would not be useful). For instance, "merge,-/ .excl" would
3160 treat the contents of .excl as absolute-path excludes,
3161 while "dir-merge,s .filt" and ":sC" would each make all their
3162 per-directory rules apply only on the sending side. If the merge rule
3163 specifies sides to affect (via the bf(s) or bf(r) modifier or both),
3164 then the rules in the file must not specify sides (via a modifier or
3165 a rule prefix such as bf(hide)).
3168 Per-directory rules are inherited in all subdirectories of the directory
3169 where the merge-file was found unless the 'n' modifier was used. Each
3170 subdirectory's rules are prefixed to the inherited per-directory rules
3171 from its parents, which gives the newest rules a higher priority than the
3172 inherited rules. The entire set of dir-merge rules are grouped together in
3173 the spot where the merge-file was specified, so it is possible to override
3174 dir-merge rules via a rule that got specified earlier in the list of global
3175 rules. When the list-clearing rule ("!") is read from a per-directory
3176 file, it only clears the inherited rules for the current merge file.
3178 Another way to prevent a single rule from a dir-merge file from being inherited is to
3179 anchor it with a leading slash. Anchored rules in a per-directory
3180 merge-file are relative to the merge-file's directory, so a pattern "/foo"
3181 would only match the file "foo" in the directory where the dir-merge filter
3184 Here's an example filter file which you'd specify via bf(--filter=". file":)
3187 tt(merge /home/user/.global-filter)nl()
3189 tt(dir-merge .rules)nl()
3194 This will merge the contents of the /home/user/.global-filter file at the
3195 start of the list and also turns the ".rules" filename into a per-directory
3196 filter file. All rules read in prior to the start of the directory scan
3197 follow the global anchoring rules (i.e. a leading slash matches at the root
3200 If a per-directory merge-file is specified with a path that is a parent
3201 directory of the first transfer directory, rsync will scan all the parent
3202 dirs from that starting point to the transfer directory for the indicated
3203 per-directory file. For instance, here is a common filter (see bf(-F)):
3205 quote(tt(--filter=': /.rsync-filter'))
3207 That rule tells rsync to scan for the file .rsync-filter in all
3208 directories from the root down through the parent directory of the
3209 transfer prior to the start of the normal directory scan of the file in
3210 the directories that are sent as a part of the transfer. (Note: for an
3211 rsync daemon, the root is always the same as the module's "path".)
3213 Some examples of this pre-scanning for per-directory files:
3216 tt(rsync -avF /src/path/ /dest/dir)nl()
3217 tt(rsync -av --filter=': ../../.rsync-filter' /src/path/ /dest/dir)nl()
3218 tt(rsync -av --filter=': .rsync-filter' /src/path/ /dest/dir)nl()
3221 The first two commands above will look for ".rsync-filter" in "/" and
3222 "/src" before the normal scan begins looking for the file in "/src/path"
3223 and its subdirectories. The last command avoids the parent-dir scan
3224 and only looks for the ".rsync-filter" files in each directory that is
3225 a part of the transfer.
3227 If you want to include the contents of a ".cvsignore" in your patterns,
3228 you should use the rule ":C", which creates a dir-merge of the .cvsignore
3229 file, but parsed in a CVS-compatible manner. You can
3230 use this to affect where the bf(--cvs-exclude) (bf(-C)) option's inclusion of the
3231 per-directory .cvsignore file gets placed into your rules by putting the
3232 ":C" wherever you like in your filter rules. Without this, rsync would
3233 add the dir-merge rule for the .cvsignore file at the end of all your other
3234 rules (giving it a lower priority than your command-line rules). For
3238 tt(cat <<EOT | rsync -avC --filter='. -' a/ b)nl()
3243 tt(rsync -avC --include=foo.o -f :C --exclude='*.old' a/ b)nl()
3246 Both of the above rsync commands are identical. Each one will merge all
3247 the per-directory .cvsignore rules in the middle of the list rather than
3248 at the end. This allows their dir-specific rules to supersede the rules
3249 that follow the :C instead of being subservient to all your rules. To
3250 affect the other CVS exclude rules (i.e. the default list of exclusions,
3251 the contents of $HOME/.cvsignore, and the value of $CVSIGNORE) you should
3252 omit the bf(-C) command-line option and instead insert a "-C" rule into
3253 your filter rules; e.g. "bf(--filter=-C)".
3255 manpagesection(LIST-CLEARING FILTER RULE)
3257 You can clear the current include/exclude list by using the "!" filter
3258 rule (as introduced in the FILTER RULES section above). The "current"
3259 list is either the global list of rules (if the rule is encountered while
3260 parsing the filter options) or a set of per-directory rules (which are
3261 inherited in their own sub-list, so a subdirectory can use this to clear
3262 out the parent's rules).
3264 manpagesection(ANCHORING INCLUDE/EXCLUDE PATTERNS)
3266 As mentioned earlier, global include/exclude patterns are anchored at the
3267 "root of the transfer" (as opposed to per-directory patterns, which are
3268 anchored at the merge-file's directory). If you think of the transfer as
3269 a subtree of names that are being sent from sender to receiver, the
3270 transfer-root is where the tree starts to be duplicated in the destination
3271 directory. This root governs where patterns that start with a / match.
3273 Because the matching is relative to the transfer-root, changing the
3274 trailing slash on a source path or changing your use of the bf(--relative)
3275 option affects the path you need to use in your matching (in addition to
3276 changing how much of the file tree is duplicated on the destination
3277 host). The following examples demonstrate this.
3279 Let's say that we want to match two source files, one with an absolute
3280 path of "/home/me/foo/bar", and one with a path of "/home/you/bar/baz".
3281 Here is how the various command choices differ for a 2-source transfer:
3284 Example cmd: rsync -a /home/me /home/you /dest nl()
3285 +/- pattern: /me/foo/bar nl()
3286 +/- pattern: /you/bar/baz nl()
3287 Target file: /dest/me/foo/bar nl()
3288 Target file: /dest/you/bar/baz nl()
3292 Example cmd: rsync -a /home/me/ /home/you/ /dest nl()
3293 +/- pattern: /foo/bar (note missing "me") nl()
3294 +/- pattern: /bar/baz (note missing "you") nl()
3295 Target file: /dest/foo/bar nl()
3296 Target file: /dest/bar/baz nl()
3300 Example cmd: rsync -a --relative /home/me/ /home/you /dest nl()
3301 +/- pattern: /home/me/foo/bar (note full path) nl()
3302 +/- pattern: /home/you/bar/baz (ditto) nl()
3303 Target file: /dest/home/me/foo/bar nl()
3304 Target file: /dest/home/you/bar/baz nl()
3308 Example cmd: cd /home; rsync -a --relative me/foo you/ /dest nl()
3309 +/- pattern: /me/foo/bar (starts at specified path) nl()
3310 +/- pattern: /you/bar/baz (ditto) nl()
3311 Target file: /dest/me/foo/bar nl()
3312 Target file: /dest/you/bar/baz nl()
3315 The easiest way to see what name you should filter is to just
3316 look at the output when using bf(--verbose) and put a / in front of the name
3317 (use the bf(--dry-run) option if you're not yet ready to copy any files).
3319 manpagesection(PER-DIRECTORY RULES AND DELETE)
3321 Without a delete option, per-directory rules are only relevant on the
3322 sending side, so you can feel free to exclude the merge files themselves
3323 without affecting the transfer. To make this easy, the 'e' modifier adds
3324 this exclude for you, as seen in these two equivalent commands:
3327 tt(rsync -av --filter=': .excl' --exclude=.excl host:src/dir /dest)nl()
3328 tt(rsync -av --filter=':e .excl' host:src/dir /dest)nl()
3331 However, if you want to do a delete on the receiving side AND you want some
3332 files to be excluded from being deleted, you'll need to be sure that the
3333 receiving side knows what files to exclude. The easiest way is to include
3334 the per-directory merge files in the transfer and use bf(--delete-after),
3335 because this ensures that the receiving side gets all the same exclude
3336 rules as the sending side before it tries to delete anything:
3338 quote(tt(rsync -avF --delete-after host:src/dir /dest))
3340 However, if the merge files are not a part of the transfer, you'll need to
3341 either specify some global exclude rules (i.e. specified on the command
3342 line), or you'll need to maintain your own per-directory merge files on
3343 the receiving side. An example of the first is this (assume that the
3344 remote .rules files exclude themselves):
3346 verb(rsync -av --filter=': .rules' --filter='. /my/extra.rules'
3347 --delete host:src/dir /dest)
3349 In the above example the extra.rules file can affect both sides of the
3350 transfer, but (on the sending side) the rules are subservient to the rules
3351 merged from the .rules files because they were specified after the
3352 per-directory merge rule.
3354 In one final example, the remote side is excluding the .rsync-filter
3355 files from the transfer, but we want to use our own .rsync-filter files
3356 to control what gets deleted on the receiving side. To do this we must
3357 specifically exclude the per-directory merge files (so that they don't get
3358 deleted) and then put rules into the local files to control what else
3359 should not get deleted. Like one of these commands:
3361 verb( rsync -av --filter=':e /.rsync-filter' --delete \
3363 rsync -avFF --delete host:src/dir /dest)
3365 manpagesection(BATCH MODE)
3367 Batch mode can be used to apply the same set of updates to many
3368 identical systems. Suppose one has a tree which is replicated on a
3369 number of hosts. Now suppose some changes have been made to this
3370 source tree and those changes need to be propagated to the other
3371 hosts. In order to do this using batch mode, rsync is run with the
3372 write-batch option to apply the changes made to the source tree to one
3373 of the destination trees. The write-batch option causes the rsync
3374 client to store in a "batch file" all the information needed to repeat
3375 this operation against other, identical destination trees.
3377 Generating the batch file once saves having to perform the file
3378 status, checksum, and data block generation more than once when
3379 updating multiple destination trees. Multicast transport protocols can
3380 be used to transfer the batch update files in parallel to many hosts
3381 at once, instead of sending the same data to every host individually.
3383 To apply the recorded changes to another destination tree, run rsync
3384 with the read-batch option, specifying the name of the same batch
3385 file, and the destination tree. Rsync updates the destination tree
3386 using the information stored in the batch file.
3388 For your convenience, a script file is also created when the write-batch
3389 option is used: it will be named the same as the batch file with ".sh"
3390 appended. This script file contains a command-line suitable for updating a
3391 destination tree using the associated batch file. It can be executed using
3392 a Bourne (or Bourne-like) shell, optionally passing in an alternate
3393 destination tree pathname which is then used instead of the original
3394 destination path. This is useful when the destination tree path on the
3395 current host differs from the one used to create the batch file.
3400 tt($ rsync --write-batch=foo -a host:/source/dir/ /adest/dir/)nl()
3401 tt($ scp foo* remote:)nl()
3402 tt($ ssh remote ./foo.sh /bdest/dir/)nl()
3406 tt($ rsync --write-batch=foo -a /source/dir/ /adest/dir/)nl()
3407 tt($ ssh remote rsync --read-batch=- -a /bdest/dir/ <foo)nl()
3410 In these examples, rsync is used to update /adest/dir/ from /source/dir/
3411 and the information to repeat this operation is stored in "foo" and
3412 "foo.sh". The host "remote" is then updated with the batched data going
3413 into the directory /bdest/dir. The differences between the two examples
3414 reveals some of the flexibility you have in how you deal with batches:
3417 it() The first example shows that the initial copy doesn't have to be
3418 local -- you can push or pull data to/from a remote host using either the
3419 remote-shell syntax or rsync daemon syntax, as desired.
3420 it() The first example uses the created "foo.sh" file to get the right
3421 rsync options when running the read-batch command on the remote host.
3422 it() The second example reads the batch data via standard input so that
3423 the batch file doesn't need to be copied to the remote machine first.
3424 This example avoids the foo.sh script because it needed to use a modified
3425 bf(--read-batch) option, but you could edit the script file if you wished to
3426 make use of it (just be sure that no other option is trying to use
3427 standard input, such as the "bf(--exclude-from=-)" option).
3432 The read-batch option expects the destination tree that it is updating
3433 to be identical to the destination tree that was used to create the
3434 batch update fileset. When a difference between the destination trees
3435 is encountered the update might be discarded with a warning (if the file
3436 appears to be up-to-date already) or the file-update may be attempted
3437 and then, if the file fails to verify, the update discarded with an
3438 error. This means that it should be safe to re-run a read-batch operation
3439 if the command got interrupted. If you wish to force the batched-update to
3440 always be attempted regardless of the file's size and date, use the bf(-I)
3441 option (when reading the batch).
3442 If an error occurs, the destination tree will probably be in a
3443 partially updated state. In that case, rsync can
3444 be used in its regular (non-batch) mode of operation to fix up the
3447 The rsync version used on all destinations must be at least as new as the
3448 one used to generate the batch file. Rsync will die with an error if the
3449 protocol version in the batch file is too new for the batch-reading rsync
3450 to handle. See also the bf(--protocol) option for a way to have the
3451 creating rsync generate a batch file that an older rsync can understand.
3452 (Note that batch files changed format in version 2.6.3, so mixing versions
3453 older than that with newer versions will not work.)
3455 When reading a batch file, rsync will force the value of certain options
3456 to match the data in the batch file if you didn't set them to the same
3457 as the batch-writing command. Other options can (and should) be changed.
3458 For instance bf(--write-batch) changes to bf(--read-batch),
3459 bf(--files-from) is dropped, and the
3460 bf(--filter)/bf(--include)/bf(--exclude) options are not needed unless
3461 one of the bf(--delete) options is specified.
3463 The code that creates the BATCH.sh file transforms any filter/include/exclude
3464 options into a single list that is appended as a "here" document to the
3465 shell script file. An advanced user can use this to modify the exclude
3466 list if a change in what gets deleted by bf(--delete) is desired. A normal
3467 user can ignore this detail and just use the shell script as an easy way
3468 to run the appropriate bf(--read-batch) command for the batched data.
3470 The original batch mode in rsync was based on "rsync+", but the latest
3471 version uses a new implementation.
3473 manpagesection(SYMBOLIC LINKS)
3475 Three basic behaviors are possible when rsync encounters a symbolic
3476 link in the source directory.
3478 By default, symbolic links are not transferred at all. A message
3479 "skipping non-regular" file is emitted for any symlinks that exist.
3481 If bf(--links) is specified, then symlinks are recreated with the same
3482 target on the destination. Note that bf(--archive) implies
3485 If bf(--copy-links) is specified, then symlinks are "collapsed" by
3486 copying their referent, rather than the symlink.
3488 Rsync can also distinguish "safe" and "unsafe" symbolic links. An
3489 example where this might be used is a web site mirror that wishes to
3490 ensure that the rsync module that is copied does not include symbolic links to
3491 bf(/etc/passwd) in the public section of the site. Using
3492 bf(--copy-unsafe-links) will cause any links to be copied as the file
3493 they point to on the destination. Using bf(--safe-links) will cause
3494 unsafe links to be omitted altogether. (Note that you must specify
3495 bf(--links) for bf(--safe-links) to have any effect.)
3497 Symbolic links are considered unsafe if they are absolute symlinks
3498 (start with bf(/)), empty, or if they contain enough ".."
3499 components to ascend from the directory being copied.
3501 Here's a summary of how the symlink options are interpreted. The list is
3502 in order of precedence, so if your combination of options isn't mentioned,
3503 use the first line that is a complete subset of your options:
3505 dit(bf(--copy-links)) Turn all symlinks into normal files (leaving no
3506 symlinks for any other options to affect).
3508 dit(bf(--links --copy-unsafe-links)) Turn all unsafe symlinks into files
3509 and duplicate all safe symlinks.
3511 dit(bf(--copy-unsafe-links)) Turn all unsafe symlinks into files, noisily
3512 skip all safe symlinks.
3514 dit(bf(--links --safe-links)) Duplicate safe symlinks and skip unsafe
3517 dit(bf(--links)) Duplicate all symlinks.
3519 manpagediagnostics()
3521 rsync occasionally produces error messages that may seem a little
3522 cryptic. The one that seems to cause the most confusion is "protocol
3523 version mismatch -- is your shell clean?".
3525 This message is usually caused by your startup scripts or remote shell
3526 facility producing unwanted garbage on the stream that rsync is using
3527 for its transport. The way to diagnose this problem is to run your
3528 remote shell like this:
3530 quote(tt(ssh remotehost /bin/true > out.dat))
3532 then look at out.dat. If everything is working correctly then out.dat
3533 should be a zero length file. If you are getting the above error from
3534 rsync then you will probably find that out.dat contains some text or
3535 data. Look at the contents and try to work out what is producing
3536 it. The most common cause is incorrectly configured shell startup
3537 scripts (such as .cshrc or .profile) that contain output statements
3538 for non-interactive logins.
3540 If you are having trouble debugging filter patterns, then
3541 try specifying the bf(-vv) option. At this level of verbosity rsync will
3542 show why each individual file is included or excluded.
3544 manpagesection(EXIT VALUES)
3548 dit(bf(1)) Syntax or usage error
3549 dit(bf(2)) Protocol incompatibility
3550 dit(bf(3)) Errors selecting input/output files, dirs
3551 dit(bf(4)) Requested action not supported: an attempt
3552 was made to manipulate 64-bit files on a platform that cannot support
3553 them; or an option was specified that is supported by the client and
3555 dit(bf(5)) Error starting client-server protocol
3556 dit(bf(6)) Daemon unable to append to log-file
3557 dit(bf(10)) Error in socket I/O
3558 dit(bf(11)) Error in file I/O
3559 dit(bf(12)) Error in rsync protocol data stream
3560 dit(bf(13)) Errors with program diagnostics
3561 dit(bf(14)) Error in IPC code
3562 dit(bf(20)) Received SIGUSR1 or SIGINT
3563 dit(bf(21)) Some error returned by code(waitpid())
3564 dit(bf(22)) Error allocating core memory buffers
3565 dit(bf(23)) Partial transfer due to error
3566 dit(bf(24)) Partial transfer due to vanished source files
3567 dit(bf(25)) The --max-delete limit stopped deletions
3568 dit(bf(30)) Timeout in data send/receive
3569 dit(bf(35)) Timeout waiting for daemon connection
3572 manpagesection(ENVIRONMENT VARIABLES)
3575 dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
3576 ignore patterns in .cvsignore files. See the bf(--cvs-exclude) option for
3578 dit(bf(RSYNC_ICONV)) Specify a default bf(--iconv) setting using this
3579 environment variable. (First supported in 3.0.0.)
3580 dit(bf(RSYNC_PROTECT_ARGS)) Specify a non-zero numeric value if you want the
3581 bf(--protect-args) option to be enabled by default, or a zero value to make
3582 sure that it is disabled by default. (First supported in 3.1.0.)
3583 dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
3584 override the default shell used as the transport for rsync. Command line
3585 options are permitted after the command name, just as in the bf(-e) option.
3586 dit(bf(RSYNC_PROXY)) The RSYNC_PROXY environment variable allows you to
3587 redirect your rsync client to use a web proxy when connecting to a
3588 rsync daemon. You should set RSYNC_PROXY to a hostname:port pair.
3589 dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
3590 password allows you to run authenticated rsync connections to an rsync
3591 daemon without user intervention. Note that this does not supply a
3592 password to a remote shell transport such as ssh; to learn how to do that,
3593 consult the remote shell's documentation.
3594 dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
3595 are used to determine the default username sent to an rsync daemon.
3596 If neither is set, the username defaults to "nobody".
3597 dit(bf(HOME)) The HOME environment variable is used to find the user's
3598 default .cvsignore file.
3603 /etc/rsyncd.conf or rsyncd.conf
3611 times are transferred as *nix time_t values
3613 When transferring to FAT filesystems rsync may re-sync
3615 See the comments on the bf(--modify-window) option.
3617 file permissions, devices, etc. are transferred as native numerical
3620 see also the comments on the bf(--delete) option
3622 Please report bugs! See the web site at
3623 url(http://rsync.samba.org/)(http://rsync.samba.org/)
3625 manpagesection(VERSION)
3627 This man page is current for version 3.1.3 of rsync.
3629 manpagesection(INTERNAL OPTIONS)
3631 The options bf(--server) and bf(--sender) are used internally by rsync,
3632 and should never be typed by a user under normal circumstances. Some
3633 awareness of these options may be needed in certain scenarios, such as
3634 when setting up a login that can only run an rsync command. For instance,
3635 the support directory of the rsync distribution has an example script
3636 named rrsync (for restricted rsync) that can be used with a restricted
3639 manpagesection(CREDITS)
3641 rsync is distributed under the GNU General Public License. See the file
3642 COPYING for details.
3644 A WEB site is available at
3645 url(http://rsync.samba.org/)(http://rsync.samba.org/). The site
3646 includes an FAQ-O-Matic which may cover questions unanswered by this
3649 The primary ftp site for rsync is
3650 url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync).
3652 We would be delighted to hear from you if you like this program.
3653 Please contact the mailing-list at rsync@lists.samba.org.
3655 This program uses the excellent zlib compression library written by
3656 Jean-loup Gailly and Mark Adler.
3658 manpagesection(THANKS)
3660 Special thanks go out to: John Van Essen, Matt McCutchen, Wesley W. Terpstra,
3661 David Dykstra, Jos Backus, Sebastian Krahmer, Martin Pool, and our
3662 gone-but-not-forgotten compadre, J.W. Schultz.
3664 Thanks also to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
3665 and David Bell. I've probably missed some people, my apologies if I have.
3669 rsync was originally written by Andrew Tridgell and Paul Mackerras.
3670 Many people have later contributed to it. It is currently maintained
3673 Mailing lists for support and development are available at
3674 url(http://lists.samba.org)(lists.samba.org)