1 mailto(rsync-bugs@samba.org)
2 manpage(rsync)(1)(30 Apr 2004)()()
3 manpagename(rsync)(faster, flexible replacement for rcp)
6 rsync [OPTION]... SRC [SRC]... [USER@]HOST:DEST
8 rsync [OPTION]... [USER@]HOST:SRC DEST
10 rsync [OPTION]... SRC [SRC]... DEST
12 rsync [OPTION]... [USER@]HOST::SRC [DEST]
14 rsync [OPTION]... SRC [SRC]... [USER@]HOST::DEST
16 rsync [OPTION]... rsync://[USER@]HOST[:PORT]/SRC [DEST]
18 rsync [OPTION]... SRC [SRC]... rsync://[USER@]HOST[:PORT]/DEST
22 rsync is a program that behaves in much the same way that rcp does,
23 but has many more options and uses the rsync remote-update protocol to
24 greatly speed up file transfers when the destination file already
27 The rsync remote-update protocol allows rsync to transfer just the
28 differences between two sets of files across the network connection, using
29 an efficient checksum-search algorithm described in the technical
30 report that accompanies this package.
32 Some of the additional features of rsync are:
35 it() support for copying links, devices, owners, groups and permissions
36 it() exclude and exclude-from options similar to GNU tar
37 it() a CVS exclude mode for ignoring the same files that CVS would ignore
38 it() can use any transparent remote shell, including ssh or rsh
39 it() does not require root privileges
40 it() pipelining of file transfers to minimize latency costs
41 it() support for anonymous or authenticated rsync servers (ideal for
45 manpagesection(GENERAL)
47 There are eight different ways of using rsync. They are:
50 it() for copying local files. This is invoked when neither
51 source nor destination path contains a : separator
53 it() for copying from the local machine to a remote machine using
54 a remote shell program as the transport (such as ssh or
55 rsh). This is invoked when the destination path contains a
58 it() for copying from a remote machine to the local machine
59 using a remote shell program. This is invoked when the source
60 contains a : separator.
62 it() for copying from a remote rsync server to the local
63 machine. This is invoked when the source path contains a ::
64 separator or an rsync:// URL.
66 it() for copying from the local machine to a remote rsync
67 server. This is invoked when the destination path contains a ::
68 separator or an rsync:// URL.
70 it() for copying from a remote machine using a remote shell
71 program as the transport, using rsync server on the remote
72 machine. This is invoked when the source path contains a ::
73 separator and the --rsh=COMMAND (aka "-e COMMAND") option is
76 it() for copying from the local machine to a remote machine
77 using a remote shell program as the transport, using rsync
78 server on the remote machine. This is invoked when the
79 destination path contains a :: separator and the
80 --rsh=COMMAND option is also provided.
82 it() for listing files on a remote machine. This is done the
83 same way as rsync transfers except that you leave off the
87 Note that in all cases (other than listing) at least one of the source
88 and destination paths must be local.
92 See the file README for installation instructions.
94 Once installed, you can use rsync to any machine that you can access via
95 a remote shell (as well as some that you can access using the rsync
96 daemon-mode protocol). For remote transfers, a modern rsync uses ssh
97 for its communications, but it may have been configured to use a
98 different remote shell by default, such as rsh or remsh.
100 You can also specify any remote shell you like, either by using the -e
101 command line option, or by setting the RSYNC_RSH environment variable.
103 One common substitute is to use ssh, which offers a high degree of
106 Note that rsync must be installed on both the source and destination
109 manpagesection(USAGE)
111 You use rsync in the same way you use rcp. You must specify a source
112 and a destination, one of which may be remote.
114 Perhaps the best way to explain the syntax is with some examples:
116 quote(rsync *.c foo:src/)
118 This would transfer all files matching the pattern *.c from the
119 current directory to the directory src on the machine foo. If any of
120 the files already exist on the remote system then the rsync
121 remote-update protocol is used to update the file by sending only the
122 differences. See the tech report for details.
124 quote(rsync -avz foo:src/bar /data/tmp)
126 This would recursively transfer all files from the directory src/bar on the
127 machine foo into the /data/tmp/bar directory on the local machine. The
128 files are transferred in "archive" mode, which ensures that symbolic
129 links, devices, attributes, permissions, ownerships, etc. are preserved
130 in the transfer. Additionally, compression will be used to reduce the
131 size of data portions of the transfer.
133 quote(rsync -avz foo:src/bar/ /data/tmp)
135 A trailing slash on the source changes this behavior to avoid creating an
136 additional directory level at the destination. You can think of a trailing
137 / on a source as meaning "copy the contents of this directory" as opposed
138 to "copy the directory by name", but in both cases the attributes of the
139 containing directory are transferred to the containing directory on the
140 destination. In other words, each of the following commands copies the
141 files in the same way, including their setting of the attributes of
144 quote(rsync -avz /src/foo /dest)
145 quote(rsync -avz /src/foo/ /dest/foo)
147 You can also use rsync in local-only mode, where both the source and
148 destination don't have a ':' in the name. In this case it behaves like
149 an improved copy command.
151 quote(rsync somehost.mydomain.com::)
153 This would list all the anonymous rsync modules available on the host
154 somehost.mydomain.com. (See the following section for more details.)
157 manpagesection(CONNECTING TO AN RSYNC SERVER)
159 It is also possible to use rsync without a remote shell as the
160 transport. In this case you will connect to a remote rsync server
161 running on TCP port 873.
163 You may establish the connection via a web proxy by setting the
164 environment variable RSYNC_PROXY to a hostname:port pair pointing to
165 your web proxy. Note that your web proxy's configuration must support
166 proxy connections to port 873.
168 Using rsync in this way is the same as using it with a remote shell except
172 it() you use a double colon :: instead of a single colon to
173 separate the hostname from the path or an rsync:// URL.
175 it() the remote server may print a message of the day when you
178 it() if you specify no path name on the remote server then the
179 list of accessible paths on the server will be shown.
181 it() if you specify no local destination then a listing of the
182 specified files on the remote server is provided.
185 Some paths on the remote server may require authentication. If so then
186 you will receive a password prompt when you connect. You can avoid the
187 password prompt by setting the environment variable RSYNC_PASSWORD to
188 the password you want to use or using the --password-file option. This
189 may be useful when scripting rsync.
191 WARNING: On some systems environment variables are visible to all
192 users. On those systems using --password-file is recommended.
194 manpagesection(CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM)
196 It is sometimes useful to be able to set up file transfers using rsync
197 server capabilities on the remote machine, while still using ssh or
198 rsh for transport. This is especially useful when you want to connect
199 to a remote machine via ssh (for encryption or to get through a
200 firewall), but you still want to have access to the rsync server
201 features (see RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM,
204 From the user's perspective, using rsync in this way is the same as
205 using it to connect to an rsync server, except that you must
206 explicitly set the remote shell program on the command line with
207 --rsh=COMMAND. (Setting RSYNC_RSH in the environment will not turn on
210 In order to distinguish between the remote-shell user and the rsync
211 server user, you can use '-l user' on your remote-shell command:
213 quote(rsync -av --rsh="ssh -l ssh-user" rsync-user@host::module[/path] local-path)
215 The "ssh-user" will be used at the ssh level; the "rsync-user" will be
216 used to check against the rsyncd.conf on the remote host.
218 manpagesection(RUNNING AN RSYNC SERVER)
220 An rsync server is configured using a configuration file. Please see the
221 rsyncd.conf(5) man page for more information. By default the configuration
222 file is called /etc/rsyncd.conf, unless rsync is running over a remote
223 shell program and is not running as root; in that case, the default name
224 is rsyncd.conf in the current directory on the remote computer
227 manpagesection(RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM)
229 See the rsyncd.conf(5) man page for full information on the rsync
230 server configuration file.
232 Several configuration options will not be available unless the remote
233 user is root (e.g. chroot, setuid/setgid, etc.). There is no need to
234 configure inetd or the services map to include the rsync server port
235 if you run an rsync server only via a remote shell program.
237 To run an rsync server out of a single-use ssh key, see this section
238 in the rsyncd.conf(5) man page.
240 manpagesection(EXAMPLES)
242 Here are some examples of how I use rsync.
244 To backup my wife's home directory, which consists of large MS Word
245 files and mail folders, I use a cron job that runs
247 quote(rsync -Cavz . arvidsjaur:backup)
249 each night over a PPP connection to a duplicate directory on my machine
252 To synchronize my samba source trees I use the following Makefile
256 rsync -avuzb --exclude '*~' samba:samba/ .
259 rsync -Cavuzb . samba:samba/
263 this allows me to sync with a CVS directory at the other end of the
264 connection. I then do cvs operations on the remote machine, which saves a
265 lot of time as the remote cvs protocol isn't very efficient.
267 I mirror a directory between my "old" and "new" ftp sites with the
270 quote(rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba")
272 this is launched from cron every few hours.
274 manpagesection(OPTIONS SUMMARY)
276 Here is a short summary of the options available in rsync. Please refer
277 to the detailed description below for a complete description.
280 -v, --verbose increase verbosity
281 -q, --quiet decrease verbosity
282 -c, --checksum always checksum
283 -a, --archive archive mode, equivalent to -rlptgoD
284 -r, --recursive recurse into directories
285 -R, --relative use relative path names
286 --no-relative turn off --relative
287 --no-implied-dirs don't send implied dirs with -R
288 -b, --backup make backups (see --suffix & --backup-dir)
289 --backup-dir make backups into this directory
290 --suffix=SUFFIX backup suffix (default ~ w/o --backup-dir)
291 -u, --update update only (don't overwrite newer files)
292 -l, --links copy symlinks as symlinks
293 -L, --copy-links copy the referent of all symlinks
294 --copy-unsafe-links copy the referent of "unsafe" symlinks
295 --safe-links ignore "unsafe" symlinks
296 -H, --hard-links preserve hard links
297 -p, --perms preserve permissions
298 -o, --owner preserve owner (root only)
299 -g, --group preserve group
300 -D, --devices preserve devices (root only)
301 -t, --times preserve times
302 -S, --sparse handle sparse files efficiently
303 -n, --dry-run show what would have been transferred
304 -W, --whole-file copy whole files, no incremental checks
305 --no-whole-file turn off --whole-file
306 -x, --one-file-system don't cross filesystem boundaries
307 -B, --block-size=SIZE checksum blocking size (default 700)
308 -e, --rsh=COMMAND specify the remote shell
309 --rsync-path=PATH specify path to rsync on the remote machine
310 --existing only update files that already exist
311 --ignore-existing ignore files that already exist on receiver
312 --delete delete files that don't exist on sender
313 --delete-excluded also delete excluded files on receiver
314 --delete-after receiver deletes after transfer, not before
315 --ignore-errors delete even if there are I/O errors
316 --max-delete=NUM don't delete more than NUM files
317 --partial keep partially transferred files
318 --force force deletion of dirs even if not empty
319 --numeric-ids don't map uid/gid values by user/group name
320 --timeout=TIME set I/O timeout in seconds
321 -I, --ignore-times turn off mod time & file size quick check
322 --size-only ignore mod time for quick check (use size)
323 --modify-window=NUM compare mod times with reduced accuracy
324 -T --temp-dir=DIR create temporary files in directory DIR
325 --compare-dest=DIR also compare received files relative to DIR
326 --link-dest=DIR create hardlinks to DIR for unchanged files
327 -P equivalent to --partial --progress
328 -z, --compress compress file data
329 -C, --cvs-exclude auto ignore files in the same way CVS does
330 --exclude=PATTERN exclude files matching PATTERN
331 --exclude-from=FILE exclude patterns listed in FILE
332 --include=PATTERN don't exclude files matching PATTERN
333 --include-from=FILE don't exclude patterns listed in FILE
334 --files-from=FILE read FILE for list of source-file names
335 -0 --from0 all file lists are delimited by nulls
336 --version print version number
337 --daemon run as an rsync daemon
338 --no-detach do not detach from the parent
339 --address=ADDRESS bind to the specified address
340 --config=FILE specify alternate rsyncd.conf file
341 --port=PORT specify alternate rsyncd port number
342 --blocking-io use blocking I/O for the remote shell
343 --no-blocking-io turn off --blocking-io
344 --stats give some file transfer stats
345 --progress show progress during transfer
346 --log-format=FORMAT log file transfers using specified format
347 --password-file=FILE get password from FILE
348 --bwlimit=KBPS limit I/O bandwidth, KBytes per second
349 --write-batch=PREFIX write batch fileset starting with PREFIX
350 --read-batch=PREFIX read batch fileset starting with PREFIX
351 -4 --ipv4 prefer IPv4
352 -6 --ipv6 prefer IPv6
353 -h, --help show this help screen
360 rsync uses the GNU long options package. Many of the command line
361 options have two variants, one short and one long. These are shown
362 below, separated by commas. Some options only have a long variant.
363 The '=' for options that take a parameter is optional; whitespace
367 dit(bf(-h, --help)) Print a short help page describing the options
370 dit(bf(--version)) print the rsync version number and exit
372 dit(bf(-v, --verbose)) This option increases the amount of information you
373 are given during the transfer. By default, rsync works silently. A
374 single -v will give you information about what files are being
375 transferred and a brief summary at the end. Two -v flags will give you
376 information on what files are being skipped and slightly more
377 information at the end. More than two -v flags should only be used if
378 you are debugging rsync.
380 dit(bf(-q, --quiet)) This option decreases the amount of information you
381 are given during the transfer, notably suppressing information messages
382 from the remote server. This flag is useful when invoking rsync from
385 dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
386 already the same size and have the same modification time-stamp.
387 This option turns off this "quick check" behavior.
389 dit(bf(--size-only)) Normally rsync will not transfer any files that are
390 already the same size and have the same modification time-stamp. With the
391 --size-only option, files will not be transferred if they have the same size,
392 regardless of timestamp. This is useful when starting to use rsync
393 after using another mirroring system which may not preserve timestamps
396 dit(bf(--modify-window)) When comparing two timestamps rsync treats
397 the timestamps as being equal if they are within the value of
398 modify_window. This is normally zero, but you may find it useful to
399 set this to a larger value in some situations. In particular, when
400 transferring to Windows FAT filesystems which cannot represent times
401 with a 1 second resolution --modify-window=1 is useful.
403 dit(bf(-c, --checksum)) This forces the sender to checksum all files using
404 a 128-bit MD4 checksum before transfer. The checksum is then
405 explicitly checked on the receiver and any files of the same name
406 which already exist and have the same checksum and size on the
407 receiver are not transferred. This option can be quite slow.
409 dit(bf(-a, --archive)) This is equivalent to -rlptgoD. It is a quick
410 way of saying you want recursion and want to preserve almost
413 Note however that bf(-a) bf(does not preserve hardlinks), because
414 finding multiply-linked files is expensive. You must separately
417 dit(bf(-r, --recursive)) This tells rsync to copy directories
418 recursively. If you don't specify this then rsync won't copy
421 dit(bf(-R, --relative)) Use relative paths. This means that the full path
422 names specified on the command line are sent to the server rather than
423 just the last parts of the filenames. This is particularly useful when
424 you want to send several different directories at the same time. For
425 example, if you used the command
427 verb(rsync foo/bar/foo.c remote:/tmp/)
429 then this would create a file called foo.c in /tmp/ on the remote
430 machine. If instead you used
432 verb(rsync -R foo/bar/foo.c remote:/tmp/)
434 then a file called /tmp/foo/bar/foo.c would be created on the remote
435 machine -- the full path name is preserved.
437 dit(bf(--no-relative)) Turn off the --relative option. This is only
438 needed if you want to use --files-from without its implied --relative
441 dit(bf(--no-implied-dirs)) When combined with the --relative option, the
442 implied directories in each path are not explicitly duplicated as part
443 of the transfer. This makes the transfer more optimal and also allows
444 the two sides to have non-matching symlinks in the implied part of the
445 path. For instance, if you transfer the file "/path/foo/file" with -R,
446 the default is for rsync to ensure that "/path" and "/path/foo" on the
447 destination exactly match the directories/symlinks of the source. Using
448 the --no-implied-dirs option would omit both of these implied dirs,
449 which means that if "/path" was a real directory on one machine and a
450 symlink of the other machine, rsync would not try to change this.
452 dit(bf(-b, --backup)) With this option, preexisting destination files are
453 renamed as each file is transferred or deleted. You can control where the
454 backup file goes and what (if any) suffix gets appended using the
455 --backup-dir and --suffix options.
457 dit(bf(--backup-dir=DIR)) In combination with the --backup option, this
458 tells rsync to store all backups in the specified directory. This is
459 very useful for incremental backups. You can additionally
460 specify a backup suffix using the --suffix option
461 (otherwise the files backed up in the specified directory
462 will keep their original filenames).
463 If DIR is a relative path, it is relative to the destination directory
464 (which changes in a recursive transfer).
466 dit(bf(--suffix=SUFFIX)) This option allows you to override the default
467 backup suffix used with the --backup (-b) option. The default suffix is a ~
468 if no --backup-dir was specified, otherwise it is an empty string.
470 dit(bf(-u, --update)) This forces rsync to skip any files for which the
471 destination file already exists and has a date later than the source
474 In the currently implementation, a difference of file format is always
475 considered to be important enough for an update, no matter what date
476 is on the objects. In other words, if the source has a directory or a
477 symlink where the destination has a file, the transfer would occur
478 regardless of the timestamps. This might change in the future (feel
479 free to comment on this on the mailing list if you have an opinion).
481 dit(bf(-l, --links)) When symlinks are encountered, recreate the
482 symlink on the destination.
484 dit(bf(-L, --copy-links)) When symlinks are encountered, the file that
485 they point to (the referent) is copied, rather than the symlink.
487 dit(bf(--copy-unsafe-links)) This tells rsync to copy the referent of
488 symbolic links that point outside the copied tree. Absolute symlinks
489 are also treated like ordinary files, and so are any symlinks in the
490 source path itself when --relative is used.
492 dit(bf(--safe-links)) This tells rsync to ignore any symbolic links
493 which point outside the copied tree. All absolute symlinks are
494 also ignored. Using this option in conjunction with --relative may
495 give unexpected results.
497 dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on
498 the remote system to be the same as the local system. Without this
499 option hard links are treated like regular files.
501 Note that rsync can only detect hard links if both parts of the link
502 are in the list of files being sent.
504 This option can be quite slow, so only use it if you need it.
506 dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
507 is not used and the whole file is sent as-is instead. The transfer may be
508 faster if this option is used when the bandwidth between the source and
509 target machines is higher than the bandwidth to disk (especially when the
510 "disk" is actually a networked filesystem). This is the default when both
511 the source and target are on the local machine.
513 dit(bf(--no-whole-file)) Turn off --whole-file, for use when it is the
516 dit(bf(-p, --perms)) This option causes rsync to set the destination
517 permissions to be the same as the source permissions.
519 Without this option, each new file gets its permissions set based on the
520 source file's permissions and the umask at the receiving end, while all
521 other files (including updated files) retain their existing permissions
522 (which is the same behavior as other file-copy utilities, such as cp).
524 dit(bf(-o, --owner)) This option causes rsync to set the owner of the
525 destination file to be the same as the source file. On most systems,
526 only the super-user can set file ownership. By default, the preservation
527 is done by name, but may fall back to using the ID number in some
528 circumstances. See the --numeric-ids option for a full discussion.
530 dit(bf(-g, --group)) This option causes rsync to set the group of the
531 destination file to be the same as the source file. If the receiving
532 program is not running as the super-user, only groups that the
533 receiver is a member of will be preserved. By default, the preservation
534 is done by name, but may fall back to using the ID number in some
535 circumstances. See the --numeric-ids option for a full discussion.
537 dit(bf(-D, --devices)) This option causes rsync to transfer character and
538 block device information to the remote system to recreate these
539 devices. This option is only available to the super-user.
541 dit(bf(-t, --times)) This tells rsync to transfer modification times along
542 with the files and update them on the remote system. Note that if this
543 option is not used, the optimization that excludes files that have not been
544 modified cannot be effective; in other words, a missing -t or -a will
545 cause the next transfer to behave as if it used -I, and all files will have
546 their checksums compared and show up in log messages even if they haven't
549 dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers,
550 instead it will just report the actions it would have taken.
552 dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
553 up less space on the destination.
555 NOTE: Don't use this option when the destination is a Solaris "tmpfs"
556 filesystem. It doesn't seem to handle seeks over null regions
557 correctly and ends up corrupting the files.
559 dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem
560 boundaries when recursing. This is useful for transferring the
561 contents of only one filesystem.
563 dit(bf(--existing)) This tells rsync not to create any new files -
564 only update files that already exist on the destination.
566 dit(bf(--ignore-existing))
567 This tells rsync not to update files that already exist on
570 dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM
571 files or directories. This is useful when mirroring very large trees
572 to prevent disasters.
574 dit(bf(--delete)) This tells rsync to delete any files on the receiving
575 side that aren't on the sending side. Files that are excluded from
576 transfer are excluded from being deleted unless you use --delete-excluded.
578 This option has no effect if directory recursion is not selected.
580 This option can be dangerous if used incorrectly! It is a very good idea
581 to run first using the dry run option (-n) to see what files would be
582 deleted to make sure important files aren't listed.
584 If the sending side detects any I/O errors then the deletion of any
585 files at the destination will be automatically disabled. This is to
586 prevent temporary filesystem failures (such as NFS errors) on the
587 sending side causing a massive deletion of files on the
588 destination. You can override this with the --ignore-errors option.
590 dit(bf(--delete-excluded)) In addition to deleting the files on the
591 receiving side that are not on the sending side, this tells rsync to also
592 delete any files on the receiving side that are excluded (see --exclude).
595 dit(bf(--delete-after)) By default rsync does file deletions on the
596 receiving side before transferring files to try to ensure that there is
597 sufficient space on the receiving filesystem. If you want to delete
598 after transferring, use the --delete-after switch. Implies --delete.
600 dit(bf(--ignore-errors)) Tells --delete to go ahead and delete files
601 even when there are I/O errors.
603 dit(bf(--force)) This options tells rsync to delete directories even if
604 they are not empty when they are to be replaced by non-directories. This
605 is only relevant without --delete because deletions are now done depth-first.
606 Requires the --recursive option (which is implied by -a) to have any effect.
608 dit(bf(-B, --block-size=BLOCKSIZE)) This controls the block size used in
609 the rsync algorithm. See the technical report for details.
611 dit(bf(-e, --rsh=COMMAND)) This option allows you to choose an alternative
612 remote shell program to use for communication between the local and
613 remote copies of rsync. Typically, rsync is configured to use ssh by
614 default, but you may prefer to use rsh on a local network.
616 If this option is used with bf([user@]host::module/path), then the
617 remote shell em(COMMAND) will be used to run an rsync server on the
618 remote host, and all data will be transmitted through that remote
619 shell connection, rather than through a direct socket connection to a
620 running rsync server on the remote host. See the section "CONNECTING
621 TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM" above.
623 Command-line arguments are permitted in COMMAND provided that COMMAND is
624 presented to rsync as a single argument. For example:
626 quote(-e "ssh -p 2234")
628 (Note that ssh users can alternately customize site-specific connect
629 options in their .ssh/config file.)
631 You can also choose the remote shell program using the RSYNC_RSH
632 environment variable, which accepts the same range of values as -e.
634 See also the --blocking-io option which is affected by this option.
636 dit(bf(--rsync-path=PATH)) Use this to specify the path to the copy of
637 rsync on the remote machine. Useful when it's not in your path. Note
638 that this is the full path to the binary, not just the directory that
641 dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
642 broad range of files that you often don't want to transfer between
643 systems. It uses the same algorithm that CVS uses to determine if
644 a file should be ignored.
646 The exclude list is initialized to:
648 quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
649 .nse_depinfo *~ #* .#* ,* _$* *$ *.old *.bak *.BAK *.orig *.rej
650 .del-* *.a *.olb *.o *.obj *.so *.exe *.Z *.elc *.ln core .svn/)
652 then files listed in a $HOME/.cvsignore are added to the list and any
653 files listed in the CVSIGNORE environment variable (all cvsignore names
654 are delimited by whitespace).
656 Finally, any file is ignored if it is in the same directory as a
657 .cvsignore file and matches one of the patterns listed therein.
658 See the bf(cvs(1)) manual for more information.
660 dit(bf(--exclude=PATTERN)) This option allows you to selectively exclude
661 certain files from the list of files to be transferred. This is most
662 useful in combination with a recursive transfer.
664 You may use as many --exclude options on the command line as you like
665 to build up the list of files to exclude.
667 See the EXCLUDE PATTERNS section for detailed information on this option.
669 dit(bf(--exclude-from=FILE)) This option is similar to the --exclude
670 option, but instead it adds all exclude patterns listed in the file
671 FILE to the exclude list. Blank lines in FILE and lines starting with
672 ';' or '#' are ignored.
673 If em(FILE) is bf(-) the list will be read from standard input.
675 dit(bf(--include=PATTERN)) This option tells rsync to not exclude the
676 specified pattern of filenames. This is useful as it allows you to
677 build up quite complex exclude/include rules.
679 See the EXCLUDE PATTERNS section for detailed information on this option.
681 dit(bf(--include-from=FILE)) This specifies a list of include patterns
683 If em(FILE) is bf(-) the list will be read from standard input.
685 dit(bf(--files-from=FILE)) Using this option allows you to specify the
686 exact list of files to transfer (as read from the specified FILE or "-"
687 for stdin). It also tweaks the default behavior of rsync to make
688 transferring just the specified files and directories easier. For
689 instance, the --relative option is enabled by default when this option
690 is used (use --no-relative if you want to turn that off), all
691 directories specified in the list are created on the destination (rather
692 than being noisily skipped without -r), and the -a (--archive) option's
693 behavior does not imply -r (--recursive) -- specify it explicitly, if
696 The file names that are read from the FILE are all relative to the
697 source dir -- any leading slashes are removed and no ".." references are
698 allowed to go higher than the source dir. For example, take this
701 quote(rsync -a --files-from=/tmp/foo /usr remote:/backup)
703 If /tmp/foo contains the string "bin" (or even "/bin"), the /usr/bin
704 directory will be created as /backup/bin on the remote host (but the
705 contents of the /usr/bin dir would not be sent unless you specified -r
706 or the names were explicitly listed in /tmp/foo). Also keep in mind
707 that the effect of the (enabled by default) --relative option is to
708 duplicate only the path info that is read from the file -- it does not
709 force the duplication of the source-spec path (/usr in this case).
711 In addition, the --files-from file can be read from the remote host
712 instead of the local host if you specify a "host:" in front of the file
713 (the host must match one end of the transfer). As a short-cut, you can
714 specify just a prefix of ":" to mean "use the remote end of the
715 transfer". For example:
717 quote(rsync -a --files-from=:/path/file-list src:/ /tmp/copy)
719 This would copy all the files specified in the /path/file-list file that
720 was located on the remote "src" host.
722 dit(bf(-0, --from0)) This tells rsync that the filenames it reads from a
723 file are terminated by a null ('\0') character, not a NL, CR, or CR+LF.
724 This affects --exclude-from, --include-from, and --files-from.
725 It does not affect --cvs-exclude (since all names read from a .cvsignore
726 file are split on whitespace).
728 dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a
729 scratch directory when creating temporary copies of the files
730 transferred on the receiving side. The default behavior is to create
731 the temporary files in the receiving directory.
733 dit(bf(--compare-dest=DIR)) This option instructs rsync to use DIR on
734 the destination machine as an additional directory to compare destination
735 files against when doing transfers if the files are missing in the
736 destination directory. This is useful for doing transfers to a new
737 destination while leaving existing files intact, and then doing a
738 flash-cutover when all files have been successfully transferred (for
739 example by moving directories around and removing the old directory,
740 although this skips files that haven't changed; see also --link-dest).
741 This option increases the usefulness of --partial because partially
742 transferred files will remain in the new temporary destination until they
743 have a chance to be completed. If DIR is a relative path, it is relative
744 to the destination directory (which changes in a recursive transfer).
746 dit(bf(--link-dest=DIR)) This option behaves like bf(--compare-dest) but
747 also will create hard links from em(DIR) to the destination directory for
748 unchanged files. Files with changed ownership or permissions will not be
750 Like bf(--compare-dest) if DIR is a relative path, it is relative
751 to the destination directory (which changes in a recursive transfer).
755 rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/
758 dit(bf(-z, --compress)) With this option, rsync compresses any data from
759 the files that it sends to the destination machine. This
760 option is useful on slow connections. The compression method used is the
761 same method that gzip uses.
763 Note this this option typically achieves better compression ratios
764 that can be achieved by using a compressing remote shell, or a
765 compressing transport, as it takes advantage of the implicit
766 information sent for matching data blocks.
768 dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
769 and user IDs rather than using user and group names and mapping them
772 By default rsync will use the username and groupname to determine
773 what ownership to give files. The special uid 0 and the special group
774 0 are never mapped via user/group names even if the --numeric-ids
775 option is not specified.
777 If a user or group has no name on the source system or it has no match
778 on the destination system, then the numeric ID
779 from the source system is used instead. See also the comments on the
780 "use chroot" setting in the rsyncd.conf manpage for information on how
781 the chroot setting affects rsync's ability to look up the names of the
782 users and groups and what you can do about it.
784 dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum I/O
785 timeout in seconds. If no data is transferred for the specified time
786 then rsync will exit. The default is 0, which means no timeout.
788 dit(bf(--daemon)) This tells rsync that it is to run as a daemon. The
789 daemon may be accessed using the bf(host::module) or
790 bf(rsync://host/module/) syntax.
792 If standard input is a socket then rsync will assume that it is being
793 run via inetd, otherwise it will detach from the current terminal and
794 become a background daemon. The daemon will read the config file
795 (rsyncd.conf) on each connect made by a client and respond to
796 requests accordingly. See the rsyncd.conf(5) man page for more
799 dit(bf(--no-detach)) When running as a daemon, this option instructs
800 rsync to not detach itself and become a background process. This
801 option is required when running as a service on Cygwin, and may also
802 be useful when rsync is supervised by a program such as
803 bf(daemontools) or AIX's bf(System Resource Controller).
804 bf(--no-detach) is also recommended when rsync is run under a
805 debugger. This option has no effect if rsync is run from inetd or
808 dit(bf(--address)) By default rsync will bind to the wildcard address
809 when run as a daemon with the --daemon option or when connecting to a
810 rsync server. The --address option allows you to specify a specific IP
811 address (or hostname) to bind to. This makes virtual hosting possible
812 in conjunction with the --config option.
814 dit(bf(--config=FILE)) This specifies an alternate config file than
815 the default. This is only relevant when --daemon is specified.
816 The default is /etc/rsyncd.conf unless the daemon is running over
817 a remote shell program and the remote user is not root; in that case
818 the default is rsyncd.conf in the current directory (typically $HOME).
820 dit(bf(--port=PORT)) This specifies an alternate TCP port number to use
821 rather than the default port 873.
823 dit(bf(--blocking-io)) This tells rsync to use blocking I/O when launching
824 a remote shell transport. If the remote shell is either rsh or remsh,
825 rsync defaults to using
826 blocking I/O, otherwise it defaults to using non-blocking I/O. (Note that
827 ssh prefers non-blocking I/O.)
829 dit(bf(--no-blocking-io)) Turn off --blocking-io, for use when it is the
832 dit(bf(--log-format=FORMAT)) This allows you to specify exactly what the
833 rsync client logs to stdout on a per-file basis. The log format is
834 specified using the same format conventions as the log format option in
837 dit(bf(--stats)) This tells rsync to print a verbose set of statistics
838 on the file transfer, allowing you to tell how effective the rsync
839 algorithm is for your data.
841 dit(bf(--partial)) By default, rsync will delete any partially
842 transferred file if the transfer is interrupted. In some circumstances
843 it is more desirable to keep partially transferred files. Using the
844 --partial option tells rsync to keep the partial file which should
845 make a subsequent transfer of the rest of the file much faster.
847 dit(bf(--progress)) This option tells rsync to print information
848 showing the progress of the transfer. This gives a bored user
850 Implies --verbose without incrementing verbosity.
852 When the file is transferring, the data looks like this:
855 782448 63% 110.64kB/s 0:00:04
858 This tells you the current file size, the percentage of the transfer that
859 is complete, the current calculated file-completion rate (including both
860 data over the wire and data being matched locally), and the estimated time
861 remaining in this transfer.
863 After the a file is complete, it the data looks like this:
866 1238099 100% 146.38kB/s 0:00:08 (5, 57.1% of 396)
869 This tells you the final file size, that it's 100% complete, the final
870 transfer rate for the file, the amount of elapsed time it took to transfer
871 the file, and the addition of a total-transfer summary in parentheses.
872 These additional numbers tell you how many files have been updated, and
873 what percent of the total number of files has been scanned.
875 dit(bf(-P)) The -P option is equivalent to --partial --progress. I
876 found myself typing that combination quite often so I created an
877 option to make it easier.
879 dit(bf(--password-file)) This option allows you to provide a password
880 in a file for accessing a remote rsync server. Note that this option
881 is only useful when accessing an rsync server using the built in
882 transport, not when using a remote shell as the transport. The file
883 must not be world readable. It should contain just the password as a
886 dit(bf(--bwlimit=KBPS)) This option allows you to specify a maximum
887 transfer rate in kilobytes per second. This option is most effective when
888 using rsync with large files (several megabytes and up). Due to the nature
889 of rsync transfers, blocks of data are sent, then if rsync determines the
890 transfer was too fast, it will wait before sending the next data block. The
891 result is an average transfer rate equaling the specified limit. A value
892 of zero specifies no limit.
894 dit(bf(--write-batch=PREFIX)) Generate a set of files that can be
895 transferred as a batch update. Each filename in the set starts with
896 PREFIX. See the "BATCH MODE" section for details.
898 dit(bf(--read-batch=PREFIX)) Apply a previously generated change batch,
899 using the fileset whose filenames start with PREFIX. See the "BATCH
900 MODE" section for details.
902 dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6
903 when creating sockets. This only affects sockets that rsync has direct
904 control over, such as the outgoing socket when directly contacting an
905 rsync daemon, or the incoming sockets that an rsync daemon uses to
906 listen for connections. One of these options may be required in older
907 versions of Linux to work around an IPv6 bug in the kernel (if you see
908 an "address already in use" error when nothing else is using the port,
909 try specifying --ipv6 or --ipv4 when starting the daemon).
913 manpagesection(EXCLUDE PATTERNS)
915 The exclude and include patterns specified to rsync allow for flexible
916 selection of which files to transfer and which files to skip.
918 Rsync builds an ordered list of include/exclude options as specified on
919 the command line. Rsync checks each file and directory
920 name against each exclude/include pattern in turn. The first matching
921 pattern is acted on. If it is an exclude pattern, then that file is
922 skipped. If it is an include pattern then that filename is not
923 skipped. If no matching include/exclude pattern is found then the
924 filename is not skipped.
926 The filenames matched against the exclude/include patterns are relative
927 to the "root of the transfer". If you think of the transfer as a
928 subtree of names that are being sent from sender to receiver, the root
929 is where the tree starts to be duplicated in the destination directory.
930 This root governs where patterns that start with a / match (see below).
932 Because the matching is relative to the transfer-root, changing the
933 trailing slash on a source path or changing your use of the --relative
934 option affects the path you need to use in your matching (in addition to
935 changing how much of the file tree is duplicated on the destination
936 system). The following examples demonstrate this.
938 Let's say that we want to match two source files, one with an absolute
939 path of "/home/me/foo/bar", and one with a path of "/home/you/bar/baz".
940 Here is how the various command choices differ for a 2-source transfer:
943 Example cmd: rsync -a /home/me /home/you /dest
944 +/- pattern: /me/foo/bar
945 +/- pattern: /you/bar/baz
946 Target file: /dest/me/foo/bar
947 Target file: /dest/you/bar/baz
949 Example cmd: rsync -a /home/me/ /home/you/ /dest
950 +/- pattern: /foo/bar (note missing "me")
951 +/- pattern: /bar/baz (note missing "you")
952 Target file: /dest/foo/bar
953 Target file: /dest/bar/baz
955 Example cmd: rsync -a --relative /home/me/ /home/you /dest
956 +/- pattern: /home/me/foo/bar (note full path)
957 +/- pattern: /home/you/bar/baz (ditto)
958 Target file: /dest/home/me/foo/bar
959 Target file: /dest/home/you/bar/baz
961 Example cmd: cd /home; rsync -a --relative me/foo you/ /dest
962 +/- pattern: /me/foo/bar (starts at specified path)
963 +/- pattern: /you/bar/baz (ditto)
964 Target file: /dest/me/foo/bar
965 Target file: /dest/you/bar/baz
968 The easiest way to see what name you should include/exclude is to just
969 look at the output when using --verbose and put a / in front of the name
970 (use the --dry-run option if you're not yet ready to copy any files).
972 Note that, when using the --recursive (-r) option (which is implied by -a),
973 every subcomponent of
974 every path is visited from the top down, so include/exclude patterns get
975 applied recursively to each subcomponent.
976 The exclude patterns actually short-circuit the directory traversal stage
977 when rsync finds the files to send. If a pattern excludes a particular
978 parent directory, it can render a deeper include pattern ineffectual
979 because rsync did not descend through that excluded section of the
982 Note also that the --include and --exclude options take one pattern
983 each. To add multiple patterns use the --include-from and
984 --exclude-from options or multiple --include and --exclude options.
986 The patterns can take several forms. The rules are:
990 it() if the pattern starts with a / then it is matched against the
991 start of the filename, otherwise it is matched against the end of
993 This is the equivalent of a leading ^ in regular expressions.
994 Thus "/foo" would match a file called "foo" at the transfer-root
995 (see above for how this is different from the filesystem-root).
996 On the other hand, "foo" would match any file called "foo"
997 anywhere in the tree because the algorithm is applied recursively from
998 top down; it behaves as if each path component gets a turn at being the
999 end of the file name.
1001 it() if the pattern ends with a / then it will only match a
1002 directory, not a file, link, or device.
1004 it() if the pattern contains a wildcard character from the set
1005 *?[ then expression matching is applied using the shell filename
1006 matching rules. Otherwise a simple string match is used.
1008 it() the double asterisk pattern "**" will match slashes while a
1009 single asterisk pattern "*" will stop at slashes.
1011 it() if the pattern contains a / (not counting a trailing /) or a "**"
1012 then it is matched against the full filename, including any leading
1013 directory. If the pattern doesn't contain a / or a "**", then it is
1014 matched only against the final component of the filename. Again,
1015 remember that the algorithm is applied recursively so "full filename" can
1016 actually be any portion of a path below the starting directory.
1018 it() if the pattern starts with "+ " (a plus followed by a space)
1019 then it is always considered an include pattern, even if specified as
1020 part of an exclude option. The prefix is discarded before matching.
1022 it() if the pattern starts with "- " (a minus followed by a space)
1023 then it is always considered an exclude pattern, even if specified as
1024 part of an include option. The prefix is discarded before matching.
1026 it() if the pattern is a single exclamation mark ! then the current
1027 include/exclude list is reset, removing all previously defined patterns.
1030 The +/- rules are most useful in a list that was read from a file, allowing
1031 you to have a single exclude list that contains both include and exclude
1032 options in the proper order.
1034 Remember that the matching occurs at every step in the traversal of the
1035 directory hierarchy, so you must be sure that all the parent directories of
1036 the files you want to include are not excluded. This is particularly
1037 important when using a trailing '*' rule. For instance, this won't work:
1040 + /some/path/this-file-will-not-be-found
1045 This fails because the parent directory "some" is excluded by the '*' rule,
1046 so rsync never visits any of the files in the "some" or "some/path"
1047 directories. One solution is to ask for all directories in the hierarchy
1048 to be included by using a single rule: --include='*/' (put it somewhere
1049 before the --exclude='*' rule). Another solution is to add specific
1050 include rules for all the parent dirs that need to be visited. For
1051 instance, this set of rules works fine:
1056 + /some/path/this-file-is-found
1057 + /file-also-included
1061 Here are some examples of exclude/include matching:
1064 it() --exclude "*.o" would exclude all filenames matching *.o
1065 it() --exclude "/foo" would exclude a file called foo in the transfer-root directory
1066 it() --exclude "foo/" would exclude any directory called foo
1067 it() --exclude "/foo/*/bar" would exclude any file called bar two
1068 levels below a directory called foo in the transfer-root directory
1069 it() --exclude "/foo/**/bar" would exclude any file called bar two
1070 or more levels below a directory called foo in the transfer-root directory
1071 it() --include "*/" --include "*.c" --exclude "*" would include all
1072 directories and C source files
1073 it() --include "foo/" --include "foo/bar.c" --exclude "*" would include
1074 only foo/bar.c (the foo/ directory must be explicitly included or
1075 it would be excluded by the "*")
1078 manpagesection(BATCH MODE)
1080 bf(Note:) Batch mode should be considered experimental in this version
1081 of rsync. The interface or behavior may change before it stabilizes.
1083 Batch mode can be used to apply the same set of updates to many
1084 identical systems. Suppose one has a tree which is replicated on a
1085 number of hosts. Now suppose some changes have been made to this
1086 source tree and those changes need to be propagated to the other
1087 hosts. In order to do this using batch mode, rsync is run with the
1088 write-batch option to apply the changes made to the source tree to one
1089 of the destination trees. The write-batch option causes the rsync
1090 client to store the information needed to repeat this operation against
1091 other destination trees in a batch update fileset (see below). The
1092 filename of each file in the fileset starts with a prefix specified by
1093 the user as an argument to the write-batch option. This fileset is
1094 then copied to each remote host, where rsync is run with the read-batch
1095 option, again specifying the same prefix, and the destination tree.
1096 Rsync updates the destination tree using the information stored in the
1097 batch update fileset.
1099 The fileset consists of 4 files:
1102 it() bf(<prefix>.rsync_argvs) command-line arguments
1103 it() bf(<prefix>.rsync_flist) rsync internal file metadata
1104 it() bf(<prefix>.rsync_csums) rsync checksums
1105 it() bf(<prefix>.rsync_delta) data blocks for file update & change
1108 The .rsync_argvs file contains a command-line suitable for updating a
1109 destination tree using that batch update fileset. It can be executed
1110 using a Bourne(-like) shell, optionally passing in an alternate
1111 destination tree pathname which is then used instead of the original
1112 path. This is useful when the destination tree path differs from the
1113 original destination tree path.
1115 Generating the batch update fileset once saves having to perform the
1116 file status, checksum and data block generation more than once when
1117 updating multiple destination trees. Multicast transport protocols can
1118 be used to transfer the batch update files in parallel to many hosts at
1119 once, instead of sending the same data to every host individually.
1124 $ rsync --write-batch=pfx -a /source/dir/ /adest/dir/
1125 $ rcp pfx.rsync_* remote:
1126 $ ssh remote rsync --read-batch=pfx -a /bdest/dir/
1128 $ ssh remote ./pfx.rsync_argvs /bdest/dir/
1131 In this example, rsync is used to update /adest/dir/ with /source/dir/
1132 and the information to repeat this operation is stored in the files
1133 pfx.rsync_*. These files are then copied to the machine named "remote".
1134 Rsync is then invoked on "remote" to update /bdest/dir/ the same way as
1135 /adest/dir/. The last line shows the rsync_argvs file being used to
1140 The read-batch option expects the destination tree it is meant to update
1141 to be identical to the destination tree that was used to create the
1142 batch update fileset. When a difference between the destination trees
1143 is encountered the update will fail at that point, leaving the
1144 destination tree in a partially updated state. In that case, rsync can
1145 be used in its regular (non-batch) mode of operation to fix up the
1148 The rsync version used on all destinations should be identical to the
1149 one used on the original destination.
1151 The -z/--compress option does not work in batch mode and yields a usage
1152 error. A separate compression tool can be used instead to reduce the
1153 size of the batch update files for transport to the destination.
1155 The -n/--dryrun option does not work in batch mode and yields a runtime
1158 See bf(http://www.ils.unc.edu/i2dsi/unc_rsync+.html) for papers and technical
1161 manpagesection(SYMBOLIC LINKS)
1163 Three basic behaviors are possible when rsync encounters a symbolic
1164 link in the source directory.
1166 By default, symbolic links are not transferred at all. A message
1167 "skipping non-regular" file is emitted for any symlinks that exist.
1169 If bf(--links) is specified, then symlinks are recreated with the same
1170 target on the destination. Note that bf(--archive) implies
1173 If bf(--copy-links) is specified, then symlinks are "collapsed" by
1174 copying their referent, rather than the symlink.
1176 rsync also distinguishes "safe" and "unsafe" symbolic links. An
1177 example where this might be used is a web site mirror that wishes
1178 ensure the rsync module they copy does not include symbolic links to
1179 bf(/etc/passwd) in the public section of the site. Using
1180 bf(--copy-unsafe-links) will cause any links to be copied as the file
1181 they point to on the destination. Using bf(--safe-links) will cause
1182 unsafe links to be omitted altogether.
1184 Symbolic links are considered unsafe if they are absolute symlinks
1185 (start with bf(/)), empty, or if they contain enough bf("..")
1186 components to ascend from the directory being copied.
1188 manpagesection(DIAGNOSTICS)
1190 rsync occasionally produces error messages that may seem a little
1191 cryptic. The one that seems to cause the most confusion is "protocol
1192 version mismatch - is your shell clean?".
1194 This message is usually caused by your startup scripts or remote shell
1195 facility producing unwanted garbage on the stream that rsync is using
1196 for its transport. The way to diagnose this problem is to run your
1197 remote shell like this:
1200 ssh remotehost /bin/true > out.dat
1203 then look at out.dat. If everything is working correctly then out.dat
1204 should be a zero length file. If you are getting the above error from
1205 rsync then you will probably find that out.dat contains some text or
1206 data. Look at the contents and try to work out what is producing
1207 it. The most common cause is incorrectly configured shell startup
1208 scripts (such as .cshrc or .profile) that contain output statements
1209 for non-interactive logins.
1211 If you are having trouble debugging include and exclude patterns, then
1212 try specifying the -vv option. At this level of verbosity rsync will
1213 show why each individual file is included or excluded.
1215 manpagesection(EXIT VALUES)
1219 dit(bf(1)) Syntax or usage error
1220 dit(bf(2)) Protocol incompatibility
1221 dit(bf(3)) Errors selecting input/output files, dirs
1222 dit(bf(4)) Requested action not supported: an attempt
1223 was made to manipulate 64-bit files on a platform that cannot support
1224 them; or an option was specified that is supported by the client and
1226 dit(bf(5)) Error starting client-server protocol
1227 dit(bf(10)) Error in socket I/O
1228 dit(bf(11)) Error in file I/O
1229 dit(bf(12)) Error in rsync protocol data stream
1230 dit(bf(13)) Errors with program diagnostics
1231 dit(bf(14)) Error in IPC code
1232 dit(bf(20)) Received SIGUSR1 or SIGINT
1233 dit(bf(21)) Some error returned by waitpid()
1234 dit(bf(22)) Error allocating core memory buffers
1235 dit(bf(23)) Partial transfer due to error
1236 dit(bf(24)) Partial transfer due to vanished source files
1237 dit(bf(30)) Timeout in data send/receive
1240 manpagesection(ENVIRONMENT VARIABLES)
1244 dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
1245 ignore patterns in .cvsignore files. See the --cvs-exclude option for
1248 dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
1249 override the default shell used as the transport for rsync. Command line
1250 options are permitted after the command name, just as in the -e option.
1252 dit(bf(RSYNC_PROXY)) The RSYNC_PROXY environment variable allows you to
1253 redirect your rsync client to use a web proxy when connecting to a
1254 rsync daemon. You should set RSYNC_PROXY to a hostname:port pair.
1256 dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
1257 password allows you to run authenticated rsync connections to an rsync
1258 daemon without user intervention. Note that this does not supply a
1259 password to a shell transport such as ssh.
1261 dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
1262 are used to determine the default username sent to an rsync server.
1263 If neither is set, the username defaults to "nobody".
1265 dit(bf(HOME)) The HOME environment variable is used to find the user's
1266 default .cvsignore file.
1272 /etc/rsyncd.conf or rsyncd.conf
1278 manpagediagnostics()
1282 times are transferred as unix time_t values
1284 When transferring to FAT filesystems rsync may re-sync
1286 See the comments on the --modify-window option.
1288 file permissions, devices, etc. are transferred as native numerical
1291 see also the comments on the --delete option
1293 Please report bugs! See the website at
1294 url(http://rsync.samba.org/)(http://rsync.samba.org/)
1296 manpagesection(CREDITS)
1298 rsync is distributed under the GNU public license. See the file
1299 COPYING for details.
1301 A WEB site is available at
1302 url(http://rsync.samba.org/)(http://rsync.samba.org/). The site
1303 includes an FAQ-O-Matic which may cover questions unanswered by this
1306 The primary ftp site for rsync is
1307 url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync).
1309 We would be delighted to hear from you if you like this program.
1311 This program uses the excellent zlib compression library written by
1312 Jean-loup Gailly and Mark Adler.
1314 manpagesection(THANKS)
1316 Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
1317 and David Bell for helpful suggestions, patches and testing of rsync.
1318 I've probably missed some people, my apologies if I have.
1320 Especial thanks also to: David Dykstra, Jos Backus, Sebastian Krahmer,
1321 Martin Pool, Wayne Davison.
1325 rsync was originally written by Andrew Tridgell and Paul Mackerras.
1326 Many people have later contributed to it.
1328 Mailing lists for support and development are available at
1329 url(http://lists.samba.org)(lists.samba.org)