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://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. You can also use a rsync:// URL if no username
65 it() for copying from the local machine to a remote rsync
66 server. This is invoked when the destination path contains a ::
69 it() for listing files on a remote machine. This is done the
70 same way as rsync transfers except that you leave off the
74 Note that in all cases at least one of the source and destination
79 See the file README for installation instructions.
81 Once installed you can use rsync to any machine that you can use rsh
82 to. rsync uses rsh for its communications, unless both the source and
83 destination are local.
85 You can also specify a alternative to rsh, by either using the -e
86 command line option, or by setting the RSYNC_RSH environment variable.
88 One common substitute is to use ssh, which offers a high degree of
91 Note that rsync must be installed on both the source and destination
96 You use rsync in the same way you use rcp. You must specify a source
97 and a destination, one of which may be remote.
99 Perhaps the best way to explain the syntax is some examples:
101 quote(rsync *.c foo:src/)
103 this would transfer all files matching the pattern *.c from the
104 current directory to the directory src on the machine foo. If any of
105 the files already exist on the remote system then the rsync
106 remote-update protocol is used to update the file by sending only the
107 differences. See the tech report for details.
109 quote(rsync -avz foo:src/bar /data/tmp)
111 recursively transfer all files from the directory src/bar on the
112 machine foo into the /data/tmp/bar directory on the local machine. The
113 files are transferred in "archive" mode, which ensures that symbolic
114 links, devices, attributes, permissions, ownerships etc are preserved
115 in the transfer. Additionally compression will be used to reduce the
116 size of data portions of the transfer.
118 quote(rsync -avz foo:src/bar/ /data/tmp)
120 With a trailing slash on the source this behavior changes to transfer
121 all files from the directory src/bar on the machine foo into the
122 /data/tmp/. With a trailing / on a source name it means "copy the
123 contents of this directory". Without a trailing slash it means "copy
124 the directory". This difference becomes particularly important when
125 using the --delete option.
127 You can also use rsync in local-only mode, where both the source and
128 destination don't have a ':' in the name. In this case it behaves like
129 an improved copy command.
132 manpagesection(CONNECTING TO AN RSYNC SERVER)
134 It is also possible to use rsync without using rsh or ssh as the
135 transport. In this case you will connect to a remote rsync server
136 running on TCP port 873.
138 Using rsync in this was is the same as using it with rsh or ssh except
142 it() you use a double colon :: instead of a single colon to
143 separate the hostname from the path.
145 it() the remote server may print a message of the day when you
148 it() if you specify no path name on the remote server then the
149 list of accessible paths on the server will be shown.
151 it() if you specify no local destination then a listing of the
152 specified files on the remote server is provided
155 Some paths on the remote server may require authentication. If so then
156 you will receive a password prompt when you connect. You can avoid the
157 password prompt by setting the environment variable RSYNC_PASSWORD to
158 the password you want to use. This may be useful when scripting rsync.
160 manpagesection(RUNNING AN RSYNC SERVER)
162 An rsync server is configured using a config file which by default is
163 called /etc/rsyncd.conf. Please see the rsyncd.conf(5) man page for more
166 manpagesection(EXAMPLES)
168 Here are some examples of how I use rsync.
170 To backup my wife's home directory, which consists of large MS word
171 files and mail folders I use a cron job that runs
173 quote(rsync -Cavz . arvidsjaur:backup)
175 each night over a PPP link to a duplicate directory on my machine
178 To synchronize my samba source trees I use the following Makefile
182 rsync -avuzb --exclude '*~' samba:samba/ .
185 rsync -Cavuzb . samba:samba/
189 this allows me to sync with a CVS directory at the other end of the
190 link. I then do cvs operations on the remote machine, which saves a
191 lot of time as the remote cvs protocol isn't very efficient.
193 I mirror a directory between my "old" and "new" ftp sites with the
196 quote(rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba")
198 this is launched from cron every few hours.
200 manpagesection(OPTIONS SUMMARY)
202 Here is a short summary of the options avalable in rsync. Please refer
203 to the detailed description below for a complete description.
206 Usage: rsync [OPTION]... SRC [USER@]HOST:DEST
207 or rsync [OPTION]... [USER@]HOST:SRC DEST
208 or rsync [OPTION]... SRC DEST
209 or rsync [OPTION]... [USER@]HOST::SRC DEST
210 or rsync [OPTION]... SRC [USER@]HOST::DEST
211 or rsync [OPTION]... rsync://HOST[:PORT]/SRC DEST
214 -v, --verbose increase verbosity
215 -c, --checksum always checksum
216 -a, --archive archive mode
217 -r, --recursive recurse into directories
218 -R, --relative use relative path names
219 -b, --backup make backups (default ~ extension)
220 -u, --update update only (don't overwrite newer files)
221 -l, --links preserve soft links
222 -L, --copy-links treat soft links like regular files
223 --safe-links ignore links outside the destination tree
224 -H, --hard-links preserve hard links
225 -p, --perms preserve permissions
226 -o, --owner preserve owner (root only)
227 -g, --group preserve group
228 -D, --devices preserve devices (root only)
229 -t, --times preserve times
230 -S, --sparse handle sparse files efficiently
231 -n, --dry-run show what would have been transferred
232 -W, --whole-file copy whole files, no incremental checks
233 -x, --one-file-system don't cross filesystem boundaries
234 -B, --block-size=SIZE checksum blocking size
235 -e, --rsh=COMMAND specify rsh replacement
236 --rsync-path=PATH specify path to rsync on the remote machine
237 -C, --cvs-exclude auto ignore files in the same way CVS does
238 --delete delete files that don't exist on the sending side
239 --partial keep partially transferred files
240 --force force deletion of directories even if not empty
241 --numeric-ids don't map uid/gid values by user/group name
242 --timeout=TIME set IO timeout in seconds
243 -I, --ignore-times don't exclude files that match length and time
244 -T --temp-dir=DIR create temporary files in directory DIR
245 --compare-dest=DIR also compare destination files relative to DIR
246 -z, --compress compress file data
247 --exclude=PATTERN exclude files matching PATTERN
248 --exclude-from=FILE exclude files listed in FILE
249 --include=PATTERN don't exclude files matching PATTERN
250 --include-from=FILE don't exclude files listed in FILE
251 --suffix=SUFFIX override backup suffix
252 --version print version number
253 --daemon run as a rsync daemon
254 --config=FILE specify alternate rsyncd.conf file
255 --port=PORT specify alternate rsyncd port number
256 --stats give some file transfer stats
257 --progress show progress during transfer
258 --log-format=FORMAT log file transfers using specified format
259 -h, --help show this help screen
264 rsync uses the GNU long options package. Many of the command line
265 options have two variants, one short and one long. These are shown
266 below separated by commas. Some options only have a long variant.
269 dit(bf(-h, --help)) Print a short help page describing the options
272 dit(bf(--version)) print the rsync version number and exit
274 dit(bf(-v, --verbose)) This option increases the amount of information you
275 are given during the transfer. By default rsync works silently. A
276 single -v will give you information about what files are being
277 transferred and a brief summary at the end. Two -v flags will give you
278 information on what files are being skipped and slightly more
279 information at the end. More than two -v flags should only be used if
280 you are debugging rsync
282 dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
283 already the same length and have the same time-stamp. This option turns
286 dit(bf(-c, --checksum)) This forces the sender to checksum all files using
287 a 128-bit MD4 checksum before transfer. The checksum is then
288 explicitly checked on the receiver and any files of the same name
289 which already exist and have the same checksum and size on the
290 receiver are skipped. This option can be quite slow.
292 dit(bf(-a, --archive)) This is equivalent to -rlptDg. It is a quick way
293 of saying I want recursion and want to preserve everything.
295 Note: if the user launching rsync is root then the -o option (preserve
296 uid) is also implied.
298 dit(bf(-r, --recursive)) This tells rsync to copy directories recursively
300 dit(bf(-R, --relative)) Use relative paths. This means that the full path
301 names specified on the command line are sent to the server rather than
302 just the last parts of the filenames. This is particularly useful when
303 you want to sent several different directories at the same time. For
304 example if you used the command
306 verb(rsync foo/bar/foo.c remote:/tmp/)
308 then this would create a file called foo.c in /tmp/ on the remote
309 machine. If instead you used
311 verb(rsync -R foo/bar/foo.c remote:/tmp/)
313 then a file called /tmp/foo/bar/foo.c would be created on the remote
314 machine. The full path name is preserved.
316 dit(bf(-b, --backup)) With this option preexisting destination files are
317 renamed with a ~ extension as each file is transferred. You can
318 control the backup suffix using the --suffix option.
320 dit(bf(-u, --update)) This forces rsync to skip any files for which the
321 destination file already exists and has a date later than the source
324 dit(bf(-l, --links)) This tells rsync to recreate symbolic links on the
325 remote system to be the same as the local system. Without this
326 option all symbolic links are skipped.
328 dit(bf(-L, --copy-links)) This tells rsync to treat symbolic links just
331 dit(bf(--safe-links)) This tells rsync to ignore any symbolic links
332 which point outside the destination tree. All absolute symlinks are
333 also ignored. Using this option in conjunction with --relative may
334 give unexpecetd results.
336 dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on
337 the remote system to be the same as the local system. Without this
338 option hard links are treated like regular files.
340 Note that rsync can only detect hard links if both parts of the link
341 are in the list of files being sent.
343 This option can be quite slow, so only use it if you need it.
345 dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
346 is not used and the whole file is sent as-is instead. This may be
347 useful when using rsync with a local machine.
349 dit(bf(--partial)) By default rsync will delete any partially
350 transferred file if the transfer is interrupted. In some circumstances
351 it is more desirable to keep partially transferred files. Using the
352 --partial option tells rsync to keep the partial file which should
353 make a subsequent transfer of the rest of the file much faster.
355 dit(bf(-p, --perms)) This option causes rsync to update the remote
356 permissions to be the same as the local permissions.
358 dit(bf(-o, --owner)) This option causes rsync to update the remote owner
359 of the file to be the same as the local owner. This is only available
360 to the super-user. Note that if the source system is a daemon using chroot,
361 the --numeric-ids option is implied because the source system cannot get
362 access to the user names.
364 dit(bf(-g, --group)) This option causes rsync to update the remote group
365 of the file to be the same as the local group. Note that if the source
366 system is a daemon using chroot, the --numeric-ids option is implied because
367 the source system cannot get access to the group names.
369 dit(bf(-D, --devices)) This option causes rsync to transfer character and
370 block device information to the remote system to recreate these
371 devices. This option is only available to the super-user.
373 dit(bf(-t, --times)) This tells rsync to transfer modification times along
374 with the files and update them on the remote system
376 dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers,
377 instead it will just report the actions it would have taken.
379 dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
380 up less space on the destination.
382 NOTE: Don't use this option when the destination is a Solaris "tmpfs"
383 filesystem. It doesn't seem to handle seeks over null regions
384 correctly and ends up corrupting the files.
386 dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem
387 boundaries when recursing. This is useful for transferring the
388 contents of only one filesystem.
390 dit(bf(--delete)) This tells rsync to delete any files on the receiving
391 side that aren't on the sending side. This option can be dangerous if
394 It is a very good idea to run first using the dry run option (-n) to
395 see what files would be deleted to make sure important files aren't
398 rsync 1.6.4 changed the behavior of --delete to make it less
399 dangerous. rsync now only scans directories on the receiving side
400 that are explicitly transferred from the sending side. Only files in
401 these directories are deleted.
403 Still, it is probably easy to get burnt with this option. The moral
404 of the story is to use the -n option until you get used to the
405 behavior of --delete.
407 If the sending side detects any IO errors then the deletion of any
408 files at the destination will be automatically disabled. This is to
409 prevent temporary filesystem failures (such as NFS errors) on the
410 sending side causing a massive deletion of files on the
413 dit(bf(--force)) This options tells rsync to delete directories even if
414 they are not empty. This applies to both the --delete option and to
415 cases where rsync tries to copy a normal file but the destination
416 contains a directory of the same name. Normally rsync will refuse to
417 do a recursive directory deletion in such cases, by using --force
418 the recursive deletion will be done.
420 Use this option with caution!
422 dit(bf(-B , --block_size BLOCKSIZE)) This controls the block size used in
423 the rsync algorithm. See the technical report for details.
425 dit(bf(-e, --rsh COMMAND)) This option allows you to choose an alternative
426 remote shell program to use for communication between the local and
427 remote copies of rsync. By default rsync will use rsh, but you may
428 like to instead use ssh because of its high security.
430 You can also choose the remote shell program using the RSYNC_RSH
431 environment variable.
433 dit(bf(--rsync-path PATH)) Use this to specify the path to the copy of
434 rsync on the remote machine. Useful when its not in your path.
436 dit(bf(--exclude pattern)) This option allows you to selectively exclude
437 certain files from the list of files to be transferred. This is most
438 useful in combination with a recursive transfer.
440 You may use as many --exclude options on the command line as you like
441 to build up the list of files to exclude.
443 See the section of exclude patterns for information on the syntax of
446 dit(bf(--exclude-from FILE)) This option is similar to the --exclude
447 option, but instead it adds all filenames listed in the file FILE to
450 dit(bf(--include pattern)) This option tells rsync to not exclude the
451 specified pattern of filenames. This is useful as it allows you to
452 build up quite complex exclude/include rules.
454 See the section of exclude patterns for information on the syntax of
457 dit(bf(--include-from FILE)) This specifies a list of include patterns
460 dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
461 broad range of files that you often don't want to transfer between
462 systems. It uses the same algorithm that CVS uses to determine if
463 a file should be ignored.
465 The exclude list is initialized to:
467 quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
468 .nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-*
469 *.a *.o *.obj *.so *.Z *.elc *.ln core)
471 then files listed in a $HOME/.cvsignore are added to the list and any
472 files listed in the CVSIGNORE environment variable (space delimited).
474 Finally in each directory any files listed in the .cvsignore file in
475 that directory are added to the list.
477 dit(bf(--suffix SUFFIX)) This option allows you to override the default
478 backup suffix used with the -b option. The default is a ~.
480 dit(bf(--csum-length LENGTH)) By default the primary checksum used in
481 rsync is a very strong 16 byte MD4 checksum. In most cases you will
482 find that a truncated version of this checksum is quite efficient, and
483 this will decrease the size of the checksum data sent over the link,
484 making things faster.
486 You can choose the number of bytes in the truncated checksum using the
487 --csum-length option. Any value less than or equal to 16 is valid.
489 Note that if you use this option then you run the risk of ending up
490 with an incorrect target file. The risk with a value of 16 is
491 microscopic and can be safely ignored (the universe will probably end
492 before it fails) but with smaller values the risk is higher.
494 Current versions of rsync actually use an adaptive algorithm for the
495 checksum length by default, using a 16 byte file checksum to determine
496 if a 2nd pass is required with a longer block checksum. Only use this
497 option if you have read the source code and know what you are doing.
499 dit(bf(-T, --temp-dir DIR)) This option instructs rsync to use DIR as a
500 scratch directory when creating temporary copies of the files
501 transferred on the receiving side. The default behavior is to create
502 the temporary files in the receiving directory.
504 dit(bf(--compare-dest DIR)) This option instructs rsync to use DIR as an
505 additional directory to compare destination files against when doing
506 transfers. This is useful for doing transfers to a new destination while
507 leaving existing files intact, and then doing a flash-cutover when all
508 files have been successfully transfered (for example by moving directories
509 around and removing the old directory). This option increases the
510 usefulness of --partial because partially transferred files will remain in
511 the new temporary destination until they have a chance to be completed.
512 If DIR is a relative path, it is relative to the destination directory.
514 dit(bf(-z, --compress)) With this option, rsync compresses any data from
515 the source file(s) which it sends to the destination machine. This
516 option is useful on slow links. The compression method used is the
517 same method that gzip uses.
519 Note this this option typically achieves better compression ratios
520 that can be achieved by using a compressing remote shell, or a
521 compressing transport, as it takes advantage of the implicit
522 information sent for matching data blocks.
524 dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
525 and user ids rather than using user and group names and mapping them
528 By default rsync will use the user name and group name to determine
529 what ownership to give files. The special uid 0 and the special group
530 0 and never mapped via user/group names even if the --numeric-ids
531 option is not specified.
533 If the source system is a daemon using chroot, or if a user or group name
534 does not exist on the destination system, then the numeric id from the
535 source system is used instead.
537 dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum IO
538 timeout in seconds. If no data is transferred for the specified time
539 then rsync will exit. The default is 0, which means no timeout.
541 dit(bf(--daemon)) This tells rsync that it is to run as a rsync
542 daemon. If standard input is a socket then rsync will assume that it
543 is being run via inetd, otherwise it will detach from the current
544 terminal and become a background daemon. The daemon will read the
545 config file (/etc/rsyncd.conf) on each connect made by a client and
546 respond to requests accordingly. See the rsyncd.conf(5) man page for more
549 dit(bf(--config FILE)) This specifies an alternate config file than
550 the default /etc/rsyncd.conf. This is only relevant when --daemon is
553 dit(bf(--port PORT)) This specifies an alternate TCP port number to use
554 rather than the default port 873.
556 dit(bf(--log-format=FORMAT)) Normally rsync just logs filenames as
557 they are transferred. This allows you to specify exactly what gets
558 logged on a per file basis. The log format is specified using the same
559 format conventions as the log format option in rsyncd.conf.
561 dit(bf(--stats)) This tells rsync to print a verbose set of statistics
562 on the file transfer, allowing you to tell how effective the rsync
563 algorithm is for your data. This option only works in conjunction with
564 the -v (verbose) option.
566 dit(bf(--progress)) This option tells rsync to print information
567 showing the progress of the transfer. This gives a bored user
572 manpagesection(EXCLUDE PATTERNS)
574 The exclude and include patterns specified to rsync allow for flexible
575 selection of what files to transfer and what files to skip.
577 rsync build a ordered list of include/exclude options as specified on
578 the command line. When a filename is encountered rsync then checks the
579 name against each exclude/include pattern in turn. The first matching
580 pattern is acted on. If it is an exclude pattern than that file is
581 skipped. If it is an include pattern then that filename is not
582 skipped. If no matching include/exclude pattern is found then the
583 filename is not skipped.
585 The patterns themselves can take several forms. The rules are:
588 it() if the pattern starts with a / then it is matched against the
589 start of the filename, otherwise it is matched against the end of
590 the filename. Thus /foo would match a file called foo
591 at the base of the tree whereas foo would match any file
592 called foo anywhere in the tree.
594 it() if the pattern ends with a / then it will only match a
595 directory, not a file, link or device.
597 it() if the pattern contains a wildcard character from the set
598 *?[ then regular expression matching is applied using the
599 normal shell filename matching rules. Otherwise a simple string
602 it() if the pattern contains a / (not counting a trailing /) then it
603 is matched against the full filename, including any leading
604 directory. If the pattern doesn't contain a / then it is matched
605 only against the final component of the filename.
607 it() if the pattern starts with "+ " (a plus followed by a space)
608 then it is always considered a include pattern, even if specified as
609 part of an exclude option. The "+ " part is discarded before matching.
611 it() if the pattern starts with "- " (a minus followed by a space)
612 then it is always considered a exclude pattern, even if specified as
613 part of an include option. The "- " part is discarded before matching.
615 it() if the pattern is a single exclamation mark ! then the current
616 exclude list is reset, removing all previous exclude patterns.
619 The +/- rules are most useful in exclude lists, allowing you to have a
620 single exclude list that contains both include and exclude options.
622 Here are some examples:
625 it() --exclude "*.o" would exclude all filenames matching *.o
626 it() --exclude "/foo" would exclude a file in the base directory called foo
627 it() --exclude "foo/" would exclude any directory called foo
628 it() --include "*/" --include "*.c" --exclude "*" would include all
629 directories and C source files.
632 manpagesection(DIAGNOSTICS)
634 rsync occasinally produces error messages that may seem a little
635 cryptic. The one that seems to cause the most confusion is "protocol
636 version mismatch - is your shell clean?".
638 This message is usually caused by your startup scripts or remote shell
639 facility producing unwanted garbage on the stream that rsync is using
640 for its transport. The way ot diagnose this problem is to run your
641 remote shell like this:
644 rsh remotehost /bin/true > out.dat
647 then look at out.dat. If everything is working correctly then out.dat
648 should be a zero length file. You you are getting the above error from
649 rsync then you will probably find that out.dat contains some text or
650 data. Look at the contents and try to work out what is producing
651 it. The most common cause is incorrectly configued shell startup
652 scripts (such as .cshrc or .profile) that contain output statements
653 for non-interactive logins.
655 manpagesection(ENVIRONMENT VARIABLES)
659 dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
660 ignore patterns in .cvsignore files. See the --cvs-exclude option for
663 dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
664 override the default shell used as the transport for rsync. This can
665 be used instead of the -e option.
667 dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
668 password allows you to run authenticated rsync connections to a rsync
669 daemon without user intervention. Note that this does not supply a
670 password to a shell transport such as ssh.
672 dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
673 are used to determine the default username sent to a rsync server.
675 dit(bf(HOME)) The HOME environment variable is used to find the users
676 default .cvsignore file.
692 times are transferred as unix time_t values
694 file permissions, devices etc are transferred as native numerical
697 see also the comments on the --delete option
699 Please report bugs! The rsync bug tracking system is online at
700 url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
702 manpagesection(VERSION)
703 This man page is current for version 2.0 of rsync
705 manpagesection(CREDITS)
707 rsync is distributed under the GNU public license. See the file
710 The primary ftp site for rsync is
711 url(ftp://samba.anu.edu.au/pub/rsync)(ftp://samba.anu.edu.au/pub/rsync).
713 A WEB site is available at
714 url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
716 We would be delighted to hear from you if you like this program.
718 This program uses the zlib compression library written by Jean-loup
719 Gailly and Mark Adler.
721 manpagesection(THANKS)
723 Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
724 and David Bell for helpful suggestions and testing of rsync. I've
725 probably missed some people, my apologies if I have.
730 rsync was written by Andrew Tridgell and Paul Mackerras. They may be
731 contacted via email at tridge@samba.anu.edu.au and
732 Paul.Mackerras@cs.anu.edu.au