1 mailto(rsync-bugs@samba.anu.edu.au)
2 manpage(rsync)(1)(13 May 1998)()()
3 manpagename(rsync)(faster, flexible replacement for rcp)
6 rsync [options] [user@]host:path path
8 rsync [options] path [user@]host:path
10 rsync [options] path path
12 rsync [options] [user@]host::module[/path] path
14 rsync [options] path [user@]host::module[/path]
16 rsync [options] rsync://[user@]host[:port]/module/path path
20 rsync is a program that behaves in much the same way that rcp does,
21 but has many more options and uses the rsync remote-update protocol to
22 greatly speedup file transfers when the destination file already
25 The rsync remote-update protocol allows rsync to transfer just the
26 differences between two sets of files across the network link, using
27 an efficient checksum-search algorithm described in the technical
28 report that accompanies this package.
30 Some of the additional features of rsync are:
33 it() support for copying links, devices, owners, groups and permissions
34 it() exclude and exclude-from options similar to GNU tar
35 it() a CVS exclude mode for ignoring the same files that CVS would ignore
36 it() can use any transparent remote shell, including rsh or ssh
37 it() does not require root privileges
38 it() pipelining of file transfers to minimize latency costs
39 it() support for anonymous or authenticated rsync servers (ideal for
43 manpagesection(GENERAL)
45 There are six different ways of using rsync. They are:
48 it() for copying local files. This is invoked when neither
49 source nor destination path contains a : separator
51 it() for copying from the local machine to a remote machine using
52 a remote shell program as the transport (such as rsh or
53 ssh). This is invoked when the destination path contains a
56 it() for copying from a remote machine to the local machine
57 using a remote shell program. This is invoked when the local path
58 contains a : separator.
60 it() for copying from a remote rsync server to the local
61 machine. This is invoked when the source path contains a ::
62 separator or a rsync:// URL.
64 it() for copying from the local machine to a remote rsync
65 server. This is invoked when the destination path contains a ::
68 it() for listing files on a remote machine. This is done the
69 same way as rsync transfers except that you leave off the
73 Note that in all cases at least one of the source and destination
78 See the file README for installation instructions.
80 Once installed you can use rsync to any machine that you can use rsh
81 to. rsync uses rsh for its communications, unless both the source and
82 destination are local.
84 You can also specify a alternative to rsh, by either using the -e
85 command line option, or by setting the RSYNC_RSH environment variable.
87 One common substitute is to use ssh, which offers a high degree of
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 some examples:
100 quote(rsync *.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. See the tech report for details.
108 quote(rsync -avz foo:src/bar /data/tmp)
110 recursively transfer all files from the directory src/bar on the
111 machine foo into the /data/tmp/bar directory on the local machine. The
112 files are transferred in "archive" mode, which ensures that symbolic
113 links, devices, attributes, permissions, ownerships etc are preserved
114 in the transfer. Additionally compression will be used to reduce the
115 size of data portions of the transfer.
117 quote(rsync -avz foo:src/bar/ /data/tmp)
119 With a trailing slash on the source this behavior changes to transfer
120 all files from the directory src/bar on the machine foo into the
121 /data/tmp/. With a trailing / on a source name it means "copy the
122 contents of this directory". Without a trailing slash it means "copy
123 the directory". This difference becomes particularly important when
124 using the --delete option.
126 You can also use rsync in local-only mode, where both the source and
127 destination don't have a ':' in the name. In this case it behaves like
128 an improved copy command.
131 manpagesection(CONNECTING TO AN RSYNC SERVER)
133 It is also possible to use rsync without using rsh or ssh as the
134 transport. In this case you will connect to a remote rsync server
135 running on TCP port 873.
137 Using rsync in this was is the same as using it with rsh or ssh except
141 it() you use a double colon :: instead of a single colon to
142 separate the hostname from the path.
144 it() the remote server may print a message of the day when you
147 it() if you specify no path name on the remote server then the
148 list of accessible paths on the server will be shown.
150 it() if you specify no local destination then a listing of the
151 specified files on the remote server is provided
154 Some paths on the remote server may require authentication. If so then
155 you will receive a password prompt when you connect. You can avoid the
156 password prompt by setting the environment variable RSYNC_PASSWORD to
157 the password you want to use. This may be useful when scripting rsync.
159 manpagesection(RUNNING AN RSYNC SERVER)
161 An rsync server is configured using a config file which by default is
162 called /etc/rsyncd.conf. Please see the rsyncd.conf(5) man page for more
165 manpagesection(EXAMPLES)
167 Here are some examples of how I use rsync.
169 To backup my wife's home directory, which consists of large MS word
170 files and mail folders I use a cron job that runs
172 quote(rsync -Cavz . arvidsjaur:backup)
174 each night over a PPP link to a duplicate directory on my machine
177 To synchronize my samba source trees I use the following Makefile
181 rsync -avuzb --exclude '*~' samba:samba/ .
184 rsync -Cavuzb . samba:samba/
188 this allows me to sync with a CVS directory at the other end of the
189 link. I then do cvs operations on the remote machine, which saves a
190 lot of time as the remote cvs protocol isn't very efficient.
192 I mirror a directory between my "old" and "new" ftp sites with the
195 quote(rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba")
197 this is launched from cron every few hours.
199 manpagesection(OPTIONS SUMMARY)
201 Here is a short summary of the options avalable in rsync. Please refer
202 to the detailed description below for a complete description.
205 Usage: rsync [OPTION]... SRC [USER@]HOST:DEST
206 or rsync [OPTION]... [USER@]HOST:SRC DEST
207 or rsync [OPTION]... SRC DEST
208 or rsync [OPTION]... [USER@]HOST::SRC DEST
209 or rsync [OPTION]... SRC [USER@]HOST::DEST
210 or rsync [OPTION]... rsync://[USER@]HOST[:PORT]/SRC DEST
213 -v, --verbose increase verbosity
214 -c, --checksum always checksum
215 -a, --archive archive mode
216 -r, --recursive recurse into directories
217 -R, --relative use relative path names
218 -b, --backup make backups (default ~ extension)
219 -u, --update update only (don't overwrite newer files)
220 -l, --links preserve soft links
221 -L, --copy-links treat soft links like regular files
222 --safe-links ignore links outside the destination tree
223 -H, --hard-links preserve hard links
224 -p, --perms preserve permissions
225 -o, --owner preserve owner (root only)
226 -g, --group preserve group
227 -D, --devices preserve devices (root only)
228 -t, --times preserve times
229 -S, --sparse handle sparse files efficiently
230 -n, --dry-run show what would have been transferred
231 -W, --whole-file copy whole files, no incremental checks
232 -x, --one-file-system don't cross filesystem boundaries
233 -B, --block-size=SIZE checksum blocking size
234 -e, --rsh=COMMAND specify rsh replacement
235 --rsync-path=PATH specify path to rsync on the remote machine
236 -C, --cvs-exclude auto ignore files in the same way CVS does
237 --delete delete files that don't exist on the sending side
238 --partial keep partially transferred files
239 --force force deletion of directories even if not empty
240 --numeric-ids don't map uid/gid values by user/group name
241 --timeout=TIME set IO timeout in seconds
242 -I, --ignore-times don't exclude files that match length and time
243 -T --temp-dir=DIR create temporary files in directory DIR
244 --compare-dest=DIR also compare destination files relative to DIR
245 -z, --compress compress file data
246 --exclude=PATTERN exclude files matching PATTERN
247 --exclude-from=FILE exclude files listed in FILE
248 --include=PATTERN don't exclude files matching PATTERN
249 --include-from=FILE don't exclude files listed in FILE
250 --suffix=SUFFIX override backup suffix
251 --version print version number
252 --daemon run as a rsync daemon
253 --config=FILE specify alternate rsyncd.conf file
254 --port=PORT specify alternate rsyncd port number
255 --stats give some file transfer stats
256 --progress show progress during transfer
257 --log-format=FORMAT log file transfers using specified format
258 -h, --help show this help screen
263 rsync uses the GNU long options package. Many of the command line
264 options have two variants, one short and one long. These are shown
265 below separated by commas. Some options only have a long variant.
268 dit(bf(-h, --help)) Print a short help page describing the options
271 dit(bf(--version)) print the rsync version number and exit
273 dit(bf(-v, --verbose)) This option increases the amount of information you
274 are given during the transfer. By default rsync works silently. A
275 single -v will give you information about what files are being
276 transferred and a brief summary at the end. Two -v flags will give you
277 information on what files are being skipped and slightly more
278 information at the end. More than two -v flags should only be used if
279 you are debugging rsync
281 dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
282 already the same length and have the same time-stamp. This option turns
285 dit(bf(-c, --checksum)) This forces the sender to checksum all files using
286 a 128-bit MD4 checksum before transfer. The checksum is then
287 explicitly checked on the receiver and any files of the same name
288 which already exist and have the same checksum and size on the
289 receiver are skipped. This option can be quite slow.
291 dit(bf(-a, --archive)) This is equivalent to -rlptDg. It is a quick way
292 of saying I want recursion and want to preserve everything.
294 Note: if the user launching rsync is root then the -o option (preserve
295 uid) is also implied.
297 dit(bf(-r, --recursive)) This tells rsync to copy directories recursively
299 dit(bf(-R, --relative)) Use relative paths. This means that the full path
300 names specified on the command line are sent to the server rather than
301 just the last parts of the filenames. This is particularly useful when
302 you want to sent several different directories at the same time. For
303 example if you used the command
305 verb(rsync foo/bar/foo.c remote:/tmp/)
307 then this would create a file called foo.c in /tmp/ on the remote
308 machine. If instead you used
310 verb(rsync -R foo/bar/foo.c remote:/tmp/)
312 then a file called /tmp/foo/bar/foo.c would be created on the remote
313 machine. The full path name is preserved.
315 dit(bf(-b, --backup)) With this option preexisting destination files are
316 renamed with a ~ extension as each file is transferred. You can
317 control the backup suffix using the --suffix option.
319 dit(bf(-u, --update)) This forces rsync to skip any files for which the
320 destination file already exists and has a date later than the source
323 dit(bf(-l, --links)) This tells rsync to recreate symbolic links on the
324 remote system to be the same as the local system. Without this
325 option all symbolic links are skipped.
327 dit(bf(-L, --copy-links)) This tells rsync to treat symbolic links just
330 dit(bf(--safe-links)) This tells rsync to ignore any symbolic links
331 which point outside the destination tree. All absolute symlinks are
332 also ignored. Using this option in conjunction with --relative may
333 give unexpecetd results.
335 dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on
336 the remote system to be the same as the local system. Without this
337 option hard links are treated like regular files.
339 Note that rsync can only detect hard links if both parts of the link
340 are in the list of files being sent.
342 This option can be quite slow, so only use it if you need it.
344 dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
345 is not used and the whole file is sent as-is instead. This may be
346 useful when using rsync with a local machine.
348 dit(bf(--partial)) By default rsync will delete any partially
349 transferred file if the transfer is interrupted. In some circumstances
350 it is more desirable to keep partially transferred files. Using the
351 --partial option tells rsync to keep the partial file which should
352 make a subsequent transfer of the rest of the file much faster.
354 dit(bf(-p, --perms)) This option causes rsync to update the remote
355 permissions to be the same as the local permissions.
357 dit(bf(-o, --owner)) This option causes rsync to update the remote owner
358 of the file to be the same as the local owner. This is only available
359 to the super-user. Note that if the source system is a daemon using chroot,
360 the --numeric-ids option is implied because the source system cannot get
361 access to the user names.
363 dit(bf(-g, --group)) This option causes rsync to update the remote group
364 of the file to be the same as the local group. Note that if the source
365 system is a daemon using chroot, the --numeric-ids option is implied because
366 the source system cannot get access to the group names.
368 dit(bf(-D, --devices)) This option causes rsync to transfer character and
369 block device information to the remote system to recreate these
370 devices. This option is only available to the super-user.
372 dit(bf(-t, --times)) This tells rsync to transfer modification times along
373 with the files and update them on the remote system. Note that if this
374 option is not used, the optimization that excludes files that have not been
375 modified cannot be effective; in other words, a missing -t or -a will
376 cause the next transfer to behave as if it used -I, and all files will have
377 their checksums compared and show up in log messages even if they haven't
380 dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers,
381 instead it will just report the actions it would have taken.
383 dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
384 up less space on the destination.
386 NOTE: Don't use this option when the destination is a Solaris "tmpfs"
387 filesystem. It doesn't seem to handle seeks over null regions
388 correctly and ends up corrupting the files.
390 dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem
391 boundaries when recursing. This is useful for transferring the
392 contents of only one filesystem.
394 dit(bf(--delete)) This tells rsync to delete any files on the receiving
395 side that aren't on the sending side. This option can be dangerous if
398 It is a very good idea to run first using the dry run option (-n) to
399 see what files would be deleted to make sure important files aren't
402 rsync 1.6.4 changed the behavior of --delete to make it less
403 dangerous. rsync now only scans directories on the receiving side
404 that are explicitly transferred from the sending side. Only files in
405 these directories are deleted.
407 Still, it is probably easy to get burnt with this option. The moral
408 of the story is to use the -n option until you get used to the
409 behavior of --delete.
411 If the sending side detects any IO errors then the deletion of any
412 files at the destination will be automatically disabled. This is to
413 prevent temporary filesystem failures (such as NFS errors) on the
414 sending side causing a massive deletion of files on the
417 dit(bf(--force)) This options tells rsync to delete directories even if
418 they are not empty. This applies to both the --delete option and to
419 cases where rsync tries to copy a normal file but the destination
420 contains a directory of the same name. Normally rsync will refuse to
421 do a recursive directory deletion in such cases, by using --force
422 the recursive deletion will be done.
424 Use this option with caution!
426 dit(bf(-B , --block_size BLOCKSIZE)) This controls the block size used in
427 the rsync algorithm. See the technical report for details.
429 dit(bf(-e, --rsh COMMAND)) This option allows you to choose an alternative
430 remote shell program to use for communication between the local and
431 remote copies of rsync. By default rsync will use rsh, but you may
432 like to instead use ssh because of its high security.
434 You can also choose the remote shell program using the RSYNC_RSH
435 environment variable.
437 dit(bf(--rsync-path PATH)) Use this to specify the path to the copy of
438 rsync on the remote machine. Useful when its not in your path.
440 dit(bf(--exclude pattern)) This option allows you to selectively exclude
441 certain files from the list of files to be transferred. This is most
442 useful in combination with a recursive transfer.
444 You may use as many --exclude options on the command line as you like
445 to build up the list of files to exclude.
447 See the section of exclude patterns for information on the syntax of
450 dit(bf(--exclude-from FILE)) This option is similar to the --exclude
451 option, but instead it adds all filenames listed in the file FILE to
454 dit(bf(--include pattern)) This option tells rsync to not exclude the
455 specified pattern of filenames. This is useful as it allows you to
456 build up quite complex exclude/include rules.
458 See the section of exclude patterns for information on the syntax of
461 dit(bf(--include-from FILE)) This specifies a list of include patterns
464 dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
465 broad range of files that you often don't want to transfer between
466 systems. It uses the same algorithm that CVS uses to determine if
467 a file should be ignored.
469 The exclude list is initialized to:
471 quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
472 .nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-*
473 *.a *.o *.obj *.so *.Z *.elc *.ln core)
475 then files listed in a $HOME/.cvsignore are added to the list and any
476 files listed in the CVSIGNORE environment variable (space delimited).
478 Finally in each directory any files listed in the .cvsignore file in
479 that directory are added to the list.
481 dit(bf(--suffix SUFFIX)) This option allows you to override the default
482 backup suffix used with the -b option. The default is a ~.
484 dit(bf(--csum-length LENGTH)) By default the primary checksum used in
485 rsync is a very strong 16 byte MD4 checksum. In most cases you will
486 find that a truncated version of this checksum is quite efficient, and
487 this will decrease the size of the checksum data sent over the link,
488 making things faster.
490 You can choose the number of bytes in the truncated checksum using the
491 --csum-length option. Any value less than or equal to 16 is valid.
493 Note that if you use this option then you run the risk of ending up
494 with an incorrect target file. The risk with a value of 16 is
495 microscopic and can be safely ignored (the universe will probably end
496 before it fails) but with smaller values the risk is higher.
498 Current versions of rsync actually use an adaptive algorithm for the
499 checksum length by default, using a 16 byte file checksum to determine
500 if a 2nd pass is required with a longer block checksum. Only use this
501 option if you have read the source code and know what you are doing.
503 dit(bf(-T, --temp-dir DIR)) This option instructs rsync to use DIR as a
504 scratch directory when creating temporary copies of the files
505 transferred on the receiving side. The default behavior is to create
506 the temporary files in the receiving directory.
508 dit(bf(--compare-dest DIR)) This option instructs rsync to use DIR as an
509 additional directory to compare destination files against when doing
510 transfers. This is useful for doing transfers to a new destination while
511 leaving existing files intact, and then doing a flash-cutover when all
512 files have been successfully transfered (for example by moving directories
513 around and removing the old directory, although this requires also doing
514 the transfer with -I to avoid skipping files that haven't changed). This
515 option increases the usefulness of --partial because partially transferred
516 files will remain in the new temporary destination until they have a chance
517 to be completed. If DIR is a relative path, it is relative to the
518 destination directory.
520 dit(bf(-z, --compress)) With this option, rsync compresses any data from
521 the source file(s) which it sends to the destination machine. This
522 option is useful on slow links. The compression method used is the
523 same method that gzip uses.
525 Note this this option typically achieves better compression ratios
526 that can be achieved by using a compressing remote shell, or a
527 compressing transport, as it takes advantage of the implicit
528 information sent for matching data blocks.
530 dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
531 and user ids rather than using user and group names and mapping them
534 By default rsync will use the user name and group name to determine
535 what ownership to give files. The special uid 0 and the special group
536 0 and never mapped via user/group names even if the --numeric-ids
537 option is not specified.
539 If the source system is a daemon using chroot, or if a user or group name
540 does not exist on the destination system, then the numeric id from the
541 source system is used instead.
543 dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum IO
544 timeout in seconds. If no data is transferred for the specified time
545 then rsync will exit. The default is 0, which means no timeout.
547 dit(bf(--daemon)) This tells rsync that it is to run as a rsync
548 daemon. If standard input is a socket then rsync will assume that it
549 is being run via inetd, otherwise it will detach from the current
550 terminal and become a background daemon. The daemon will read the
551 config file (/etc/rsyncd.conf) on each connect made by a client and
552 respond to requests accordingly. See the rsyncd.conf(5) man page for more
555 dit(bf(--config FILE)) This specifies an alternate config file than
556 the default /etc/rsyncd.conf. This is only relevant when --daemon is
559 dit(bf(--port PORT)) This specifies an alternate TCP port number to use
560 rather than the default port 873.
562 dit(bf(--log-format=FORMAT)) Normally rsync just logs filenames as
563 they are transferred. This allows you to specify exactly what gets
564 logged on a per file basis. The log format is specified using the same
565 format conventions as the log format option in rsyncd.conf.
567 dit(bf(--stats)) This tells rsync to print a verbose set of statistics
568 on the file transfer, allowing you to tell how effective the rsync
569 algorithm is for your data. This option only works in conjunction with
570 the -v (verbose) option.
572 dit(bf(--progress)) This option tells rsync to print information
573 showing the progress of the transfer. This gives a bored user
578 manpagesection(EXCLUDE PATTERNS)
580 The exclude and include patterns specified to rsync allow for flexible
581 selection of what files to transfer and what files to skip.
583 rsync build a ordered list of include/exclude options as specified on
584 the command line. When a filename is encountered rsync then checks the
585 name against each exclude/include pattern in turn. The first matching
586 pattern is acted on. If it is an exclude pattern than that file is
587 skipped. If it is an include pattern then that filename is not
588 skipped. If no matching include/exclude pattern is found then the
589 filename is not skipped.
591 The patterns themselves can take several forms. The rules are:
594 it() if the pattern starts with a / then it is matched against the
595 start of the filename, otherwise it is matched against the end of
596 the filename. Thus /foo would match a file called foo
597 at the base of the tree whereas foo would match any file
598 called foo anywhere in the tree.
600 it() if the pattern ends with a / then it will only match a
601 directory, not a file, link or device.
603 it() if the pattern contains a wildcard character from the set
604 *?[ then regular expression matching is applied using the
605 normal shell filename matching rules. Otherwise a simple string
608 it() if the pattern contains a / (not counting a trailing /) then it
609 is matched against the full filename, including any leading
610 directory. If the pattern doesn't contain a / then it is matched
611 only against the final component of the filename.
613 it() if the pattern starts with "+ " (a plus followed by a space)
614 then it is always considered a include pattern, even if specified as
615 part of an exclude option. The "+ " part is discarded before matching.
617 it() if the pattern starts with "- " (a minus followed by a space)
618 then it is always considered a exclude pattern, even if specified as
619 part of an include option. The "- " part is discarded before matching.
621 it() if the pattern is a single exclamation mark ! then the current
622 exclude list is reset, removing all previous exclude patterns.
625 The +/- rules are most useful in exclude lists, allowing you to have a
626 single exclude list that contains both include and exclude options.
628 Here are some examples:
631 it() --exclude "*.o" would exclude all filenames matching *.o
632 it() --exclude "/foo" would exclude a file in the base directory called foo
633 it() --exclude "foo/" would exclude any directory called foo
634 it() --include "*/" --include "*.c" --exclude "*" would include all
635 directories and C source files.
638 manpagesection(DIAGNOSTICS)
640 rsync occasinally produces error messages that may seem a little
641 cryptic. The one that seems to cause the most confusion is "protocol
642 version mismatch - is your shell clean?".
644 This message is usually caused by your startup scripts or remote shell
645 facility producing unwanted garbage on the stream that rsync is using
646 for its transport. The way ot diagnose this problem is to run your
647 remote shell like this:
650 rsh remotehost /bin/true > out.dat
653 then look at out.dat. If everything is working correctly then out.dat
654 should be a zero length file. You you are getting the above error from
655 rsync then you will probably find that out.dat contains some text or
656 data. Look at the contents and try to work out what is producing
657 it. The most common cause is incorrectly configued shell startup
658 scripts (such as .cshrc or .profile) that contain output statements
659 for non-interactive logins.
661 manpagesection(ENVIRONMENT VARIABLES)
665 dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
666 ignore patterns in .cvsignore files. See the --cvs-exclude option for
669 dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
670 override the default shell used as the transport for rsync. This can
671 be used instead of the -e option.
673 dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
674 password allows you to run authenticated rsync connections to a rsync
675 daemon without user intervention. Note that this does not supply a
676 password to a shell transport such as ssh.
678 dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
679 are used to determine the default username sent to a rsync server.
681 dit(bf(HOME)) The HOME environment variable is used to find the users
682 default .cvsignore file.
698 times are transferred as unix time_t values
700 file permissions, devices etc are transferred as native numerical
703 see also the comments on the --delete option
705 Please report bugs! The rsync bug tracking system is online at
706 url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
708 manpagesection(VERSION)
709 This man page is current for version 2.0 of rsync
711 manpagesection(CREDITS)
713 rsync is distributed under the GNU public license. See the file
716 The primary ftp site for rsync is
717 url(ftp://samba.anu.edu.au/pub/rsync)(ftp://samba.anu.edu.au/pub/rsync).
719 A WEB site is available at
720 url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
722 We would be delighted to hear from you if you like this program.
724 This program uses the zlib compression library written by Jean-loup
725 Gailly and Mark Adler.
727 manpagesection(THANKS)
729 Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
730 and David Bell for helpful suggestions and testing of rsync. I've
731 probably missed some people, my apologies if I have.
736 rsync was written by Andrew Tridgell and Paul Mackerras. They may be
737 contacted via email at tridge@samba.anu.edu.au and
738 Paul.Mackerras@cs.anu.edu.au