Document shortcoming of "unrecognised option" message.
[rsync/rsync.git] / rsync.yo
... / ...
CommitLineData
1mailto(rsync-bugs@samba.org)
2manpage(rsync)(1)(5 Jan 2001)()()
3manpagename(rsync)(faster, flexible replacement for rcp)
4manpagesynopsis()
5
6rsync [OPTION]... SRC [SRC]... [USER@]HOST:DEST
7
8rsync [OPTION]... [USER@]HOST:SRC DEST
9
10rsync [OPTION]... SRC [SRC]... DEST
11
12rsync [OPTION]... [USER@]HOST::SRC [DEST]
13
14rsync [OPTION]... SRC [SRC]... [USER@]HOST::DEST
15
16rsync [OPTION]... rsync://[USER@]HOST[:PORT]/SRC [DEST]
17
18manpagedescription()
19
20rsync is a program that behaves in much the same way that rcp does,
21but has many more options and uses the rsync remote-update protocol to
22greatly speedup file transfers when the destination file already
23exists.
24
25The rsync remote-update protocol allows rsync to transfer just the
26differences between two sets of files across the network link, using
27an efficient checksum-search algorithm described in the technical
28report that accompanies this package.
29
30Some of the additional features of rsync are:
31
32itemize(
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
40 mirroring)
41)
42
43manpagesection(GENERAL)
44
45There are six different ways of using rsync. They are:
46
47itemize(
48 it() for copying local files. This is invoked when neither
49 source nor destination path contains a : separator
50
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
54 single : separator.
55
56 it() for copying from a remote machine to the local machine
57 using a remote shell program. This is invoked when the source
58 contains a : separator.
59
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.
63
64 it() for copying from the local machine to a remote rsync
65 server. This is invoked when the destination path contains a ::
66 separator.
67
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
70 local destination.
71)
72
73Note that in all cases (other than listing) at least one of the source
74and destination paths must be local.
75
76manpagesection(SETUP)
77
78See the file README for installation instructions.
79
80Once installed you can use rsync to any machine that you can use rsh
81to. rsync uses rsh for its communications, unless both the source and
82destination are local.
83
84You can also specify an alternative to rsh, by either using the -e
85command line option, or by setting the RSYNC_RSH environment variable.
86
87One common substitute is to use ssh, which offers a high degree of
88security.
89
90Note that rsync must be installed on both the source and destination
91machines.
92
93manpagesection(USAGE)
94
95You use rsync in the same way you use rcp. You must specify a source
96and a destination, one of which may be remote.
97
98Perhaps the best way to explain the syntax is some examples:
99
100quote(rsync *.c foo:src/)
101
102this would transfer all files matching the pattern *.c from the
103current directory to the directory src on the machine foo. If any of
104the files already exist on the remote system then the rsync
105remote-update protocol is used to update the file by sending only the
106differences. See the tech report for details.
107
108quote(rsync -avz foo:src/bar /data/tmp)
109
110this would recursively transfer all files from the directory src/bar on the
111machine foo into the /data/tmp/bar directory on the local machine. The
112files are transferred in "archive" mode, which ensures that symbolic
113links, devices, attributes, permissions, ownerships etc are preserved
114in the transfer. Additionally, compression will be used to reduce the
115size of data portions of the transfer.
116
117quote(rsync -avz foo:src/bar/ /data/tmp)
118
119a trailing slash on the source changes this behavior to transfer
120all files from the directory src/bar on the machine foo into the
121/data/tmp/. A trailing / on a source name means "copy the
122contents of this directory". Without a trailing slash it means "copy
123the directory". This difference becomes particularly important when
124using the --delete option.
125
126You can also use rsync in local-only mode, where both the source and
127destination don't have a ':' in the name. In this case it behaves like
128an improved copy command.
129
130quote(rsync somehost.mydomain.com::)
131
132this would list all the anonymous rsync modules available on the host
133somehost.mydomain.com. (See the following section for more details.)
134
135
136manpagesection(CONNECTING TO AN RSYNC SERVER)
137
138It is also possible to use rsync without using rsh or ssh as the
139transport. In this case you will connect to a remote rsync server
140running on TCP port 873.
141
142You may establish the connetcion via a web proxy by setting the
143environment variable RSYNC_PROXY to a hostname:port pair pointing to
144your web proxy. Note that your web proxy must allow proxying to port
145873, this must be configured in your proxy servers ruleset.
146
147Using rsync in this way is the same as using it with rsh or ssh except
148that:
149
150itemize(
151 it() you use a double colon :: instead of a single colon to
152 separate the hostname from the path.
153
154 it() the remote server may print a message of the day when you
155 connect.
156
157 it() if you specify no path name on the remote server then the
158 list of accessible paths on the server will be shown.
159
160 it() if you specify no local destination then a listing of the
161 specified files on the remote server is provided.
162)
163
164Some paths on the remote server may require authentication. If so then
165you will receive a password prompt when you connect. You can avoid the
166password prompt by setting the environment variable RSYNC_PASSWORD to
167the password you want to use or using the --password-file option. This
168may be useful when scripting rsync.
169
170WARNING: On some systems environment variables are visible to all
171users. On those systems using --password-file is recommended.
172
173manpagesection(RUNNING AN RSYNC SERVER)
174
175An rsync server is configured using a config file which by default is
176called /etc/rsyncd.conf. Please see the rsyncd.conf(5) man page for more
177information.
178
179manpagesection(EXAMPLES)
180
181Here are some examples of how I use rsync.
182
183To backup my wife's home directory, which consists of large MS Word
184files and mail folders, I use a cron job that runs
185
186quote(rsync -Cavz . arvidsjaur:backup)
187
188each night over a PPP link to a duplicate directory on my machine
189"arvidsjaur".
190
191To synchronize my samba source trees I use the following Makefile
192targets:
193
194quote( get:nl()
195 rsync -avuzb --exclude '*~' samba:samba/ .
196
197 put:nl()
198 rsync -Cavuzb . samba:samba/
199
200 sync: get put)
201
202this allows me to sync with a CVS directory at the other end of the
203link. I then do cvs operations on the remote machine, which saves a
204lot of time as the remote cvs protocol isn't very efficient.
205
206I mirror a directory between my "old" and "new" ftp sites with the
207command
208
209quote(rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba")
210
211this is launched from cron every few hours.
212
213manpagesection(OPTIONS SUMMARY)
214
215Here is a short summary of the options available in rsync. Please refer
216to the detailed description below for a complete description.
217
218verb(
219 -v, --verbose increase verbosity
220 -q, --quiet decrease verbosity
221 -c, --checksum always checksum
222 -a, --archive archive mode
223 -r, --recursive recurse into directories
224 -R, --relative use relative path names
225 -b, --backup make backups (default ~ suffix)
226 --backup-dir make backups into this directory
227 --suffix=SUFFIX override backup suffix
228 -u, --update update only (don't overwrite newer files)
229 -l, --links preserve soft links
230 -L, --copy-links treat soft links like regular files
231 --copy-unsafe-links copy links outside the source tree
232 --safe-links ignore links outside the destination tree
233 -H, --hard-links preserve hard links
234 -p, --perms preserve permissions
235 -o, --owner preserve owner (root only)
236 -g, --group preserve group
237 -D, --devices preserve devices (root only)
238 -t, --times preserve times
239 -S, --sparse handle sparse files efficiently
240 -n, --dry-run show what would have been transferred
241 -W, --whole-file copy whole files, no incremental checks
242 -x, --one-file-system don't cross filesystem boundaries
243 -B, --block-size=SIZE checksum blocking size (default 700)
244 -e, --rsh=COMMAND specify rsh replacement
245 --rsync-path=PATH specify path to rsync on the remote machine
246 -C, --cvs-exclude auto ignore files in the same way CVS does
247 --existing only update files that already exist
248 --delete delete files that don't exist on the sending side
249 --delete-excluded also delete excluded files on the receiving side
250 --delete-after delete after transferring, not before
251 --ignore-errors delete even if there are IO errors
252 --max-delete=NUM don't delete more than NUM files
253 --partial keep partially transferred files
254 --force force deletion of directories even if not empty
255 --numeric-ids don't map uid/gid values by user/group name
256 --timeout=TIME set IO timeout in seconds
257 -I, --ignore-times don't exclude files that match length and time
258 --size-only only use file size when determining if a file should be transferred
259 --modify-window=NUM Timestamp window (seconds) for file match (default=0)
260 -T --temp-dir=DIR create temporary files in directory DIR
261 --compare-dest=DIR also compare destination files relative to DIR
262 -P equivalent to --partial --progress
263 -z, --compress compress file data
264 --exclude=PATTERN exclude files matching PATTERN
265 --exclude-from=FILE exclude patterns listed in FILE
266 --include=PATTERN don't exclude files matching PATTERN
267 --include-from=FILE don't exclude patterns listed in FILE
268 --version print version number
269 --daemon run as a rsync daemon
270 --address bind to the specified address
271 --config=FILE specify alternate rsyncd.conf file
272 --port=PORT specify alternate rsyncd port number
273 --blocking-io use blocking IO for the remote shell
274 --stats give some file transfer stats
275 --progress show progress during transfer
276 --log-format=FORMAT log file transfers using specified format
277 --password-file=FILE get password from FILE
278 --bwlimit=KBPS limit I/O bandwidth, KBytes per second
279 -h, --help show this help screen
280)
281
282manpageoptions()
283
284rsync uses the GNU long options package. Many of the command line
285options have two variants, one short and one long. These are shown
286below, separated by commas. Some options only have a long variant.
287The '=' for options that take a parameter is optional; whitespace
288can be used instead.
289
290startdit()
291dit(bf(-h, --help)) Print a short help page describing the options
292available in rsync
293
294dit(bf(--version)) print the rsync version number and exit
295
296dit(bf(-v, --verbose)) This option increases the amount of information you
297are given during the transfer. By default, rsync works silently. A
298single -v will give you information about what files are being
299transferred and a brief summary at the end. Two -v flags will give you
300information on what files are being skipped and slightly more
301information at the end. More than two -v flags should only be used if
302you are debugging rsync.
303
304dit(bf(-q, --quiet)) This option decreases the amount of information you
305are given during the transfer, notably suppressing information messages
306from the remote server. This flag is useful when invoking rsync from
307cron.
308
309dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
310already the same length and have the same time-stamp. This option turns
311off this behavior.
312
313dit(bf(--size-only)) Normally rsync will skip any files that are
314already the same length and have the same time-stamp. With the
315--size-only option files will be skipped if they have the same size,
316regardless of timestamp. This is useful when starting to use rsync
317after using another mirroring system which may not preserve timestamps
318exactly.
319
320dit(bf(--modify-window)) When comparing two timestamps rsync treats
321the timestamps as being equal if they are within the value of
322modify_window. This is normally zero, but you may find it useful to
323set this to a larger value in some situations. In particular, when
324transferring to/from FAT filesystems which cannot represent times with
325a 1 second resolution this option is useful.
326
327dit(bf(-c, --checksum)) This forces the sender to checksum all files using
328a 128-bit MD4 checksum before transfer. The checksum is then
329explicitly checked on the receiver and any files of the same name
330which already exist and have the same checksum and size on the
331receiver are skipped. This option can be quite slow.
332
333dit(bf(-a, --archive)) This is equivalent to -rlptgoD. It is a quick way
334of saying you want recursion and want to preserve everything.
335
336dit(bf(-r, --recursive)) This tells rsync to copy directories
337recursively. If you don't specify this then rsync won't copy
338directories at all.
339
340dit(bf(-R, --relative)) Use relative paths. This means that the full path
341names specified on the command line are sent to the server rather than
342just the last parts of the filenames. This is particularly useful when
343you want to send several different directories at the same time. For
344example, if you used the command
345
346verb(rsync foo/bar/foo.c remote:/tmp/)
347
348then this would create a file called foo.c in /tmp/ on the remote
349machine. If instead you used
350
351verb(rsync -R foo/bar/foo.c remote:/tmp/)
352
353then a file called /tmp/foo/bar/foo.c would be created on the remote
354machine. The full path name is preserved.
355
356dit(bf(-b, --backup)) With this option preexisting destination files are
357renamed with a ~ extension as each file is transferred. You can
358control the backup suffix using the --suffix option.
359
360dit(bf(--backup-dir=DIR)) In combination with the --backup option, this
361tells rsync to store all backups in the specified directory. This is
362very useful for incremental backups.
363
364dit(bf(--suffix=SUFFIX)) This option allows you to override the default
365backup suffix used with the -b option. The default is a ~.
366
367dit(bf(-u, --update)) This forces rsync to skip any files for which the
368destination file already exists and has a date later than the source
369file.
370
371dit(bf(-l, --links)) This tells rsync to recreate symbolic links on the
372remote system to be the same as the local system. Without this
373option, all symbolic links are skipped.
374
375dit(bf(-L, --copy-links)) This tells rsync to treat symbolic links just
376like ordinary files.
377
378dit(bf(--copy-unsafe-links)) This tells rsync to treat symbolic links that
379point outside the source tree like ordinary files. Absolute symlinks are
380also treated like ordinary files, and so are any symlinks in the source
381path itself when --relative is used.
382
383dit(bf(--safe-links)) This tells rsync to ignore any symbolic links
384which point outside the destination tree. All absolute symlinks are
385also ignored. Using this option in conjunction with --relative may
386give unexpected results.
387
388dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on
389the remote system to be the same as the local system. Without this
390option hard links are treated like regular files.
391
392Note that rsync can only detect hard links if both parts of the link
393are in the list of files being sent.
394
395This option can be quite slow, so only use it if you need it.
396
397dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
398is not used and the whole file is sent as-is instead. This may be
399useful when using rsync with a local machine.
400
401dit(bf(-p, --perms)) This option causes rsync to update the remote
402permissions to be the same as the local permissions.
403
404dit(bf(-o, --owner)) This option causes rsync to update the remote owner
405of the file to be the same as the local owner. This is only available
406to the super-user. Note that if the source system is a daemon using chroot,
407the --numeric-ids option is implied because the source system cannot get
408access to the usernames.
409
410dit(bf(-g, --group)) This option causes rsync to update the remote group
411of the file to be the same as the local group. If the receving system is
412not running as the super-user, only groups that the receiver is a member of
413will be preserved (by group name, not group id number).
414
415dit(bf(-D, --devices)) This option causes rsync to transfer character and
416block device information to the remote system to recreate these
417devices. This option is only available to the super-user.
418
419dit(bf(-t, --times)) This tells rsync to transfer modification times along
420with the files and update them on the remote system. Note that if this
421option is not used, the optimization that excludes files that have not been
422modified cannot be effective; in other words, a missing -t or -a will
423cause the next transfer to behave as if it used -I, and all files will have
424their checksums compared and show up in log messages even if they haven't
425changed.
426
427dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers,
428instead it will just report the actions it would have taken.
429
430dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
431up less space on the destination.
432
433NOTE: Don't use this option when the destination is a Solaris "tmpfs"
434filesystem. It doesn't seem to handle seeks over null regions
435correctly and ends up corrupting the files.
436
437dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem
438boundaries when recursing. This is useful for transferring the
439contents of only one filesystem.
440
441dit(bf(--existing)) This tells rsync not to create any new files -
442only update files that already exist on the destination.
443
444dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM
445files or directories. This is useful when mirroring very large trees
446to prevent disasters.
447
448dit(bf(--delete)) This tells rsync to delete any files on the receiving
449side that aren't on the sending side. Files that are excluded from
450transfer are excluded from being deleted unless you use --delete-excluded.
451
452This option has no effect if directory recursion is not selected.
453
454This option can be dangerous if used incorrectly! It is a very good idea
455to run first using the dry run option (-n) to see what files would be
456deleted to make sure important files aren't listed.
457
458If the sending side detects any IO errors then the deletion of any
459files at the destination will be automatically disabled. This is to
460prevent temporary filesystem failures (such as NFS errors) on the
461sending side causing a massive deletion of files on the
462destination.
463
464dit(bf(--delete-excluded)) In addition to deleting the files on the
465receiving side that are not on the sending side, this tells rsync to also
466delete any files on the receiving side that are excluded (see --exclude).
467
468dit(bf(--delete-after)) By default rsync does file deletions before
469transferring files to try to ensure that there is sufficient space on
470the receiving filesystem. If you want to delete after transferring
471then use the --delete-after switch.
472
473dit(bf(--force)) This options tells rsync to delete directories even if
474they are not empty. This applies to both the --delete option and to
475cases where rsync tries to copy a normal file but the destination
476contains a directory of the same name.
477
478Since this option was added, deletions were reordered to be done depth-first
479so it is hardly ever needed anymore except in very obscure cases.
480
481dit(bf(-B , --block_size=BLOCKSIZE)) This controls the block size used in
482the rsync algorithm. See the technical report for details.
483
484dit(bf(-e, --rsh=COMMAND)) This option allows you to choose an alternative
485remote shell program to use for communication between the local and
486remote copies of rsync. By default, rsync will use rsh, but you may
487like to instead use ssh because of its high security.
488
489You can also choose the remote shell program using the RSYNC_RSH
490environment variable.
491
492See also the --blocking-io option which is affected by this option.
493
494dit(bf(--rsync-path=PATH)) Use this to specify the path to the copy of
495rsync on the remote machine. Useful when it's not in your path. Note
496that this is the full path to the binary, not just the directory that
497the binary is in.
498
499dit(bf(--exclude=PATTERN)) This option allows you to selectively exclude
500certain files from the list of files to be transferred. This is most
501useful in combination with a recursive transfer.
502
503You may use as many --exclude options on the command line as you like
504to build up the list of files to exclude.
505
506See the section on exclude patterns for information on the syntax of
507this option.
508
509dit(bf(--exclude-from=FILE)) This option is similar to the --exclude
510option, but instead it adds all exclude patterns listed in the file
511FILE to the exclude list. Blank lines in FILE and lines starting with
512';' or '#' are ignored.
513
514dit(bf(--include=PATTERN)) This option tells rsync to not exclude the
515specified pattern of filenames. This is useful as it allows you to
516build up quite complex exclude/include rules.
517
518See the section of exclude patterns for information on the syntax of
519this option.
520
521dit(bf(--include-from=FILE)) This specifies a list of include patterns
522from a file.
523
524dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
525broad range of files that you often don't want to transfer between
526systems. It uses the same algorithm that CVS uses to determine if
527a file should be ignored.
528
529The exclude list is initialized to:
530
531quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
532.nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-*
533*.a *.o *.obj *.so *.Z *.elc *.ln core)
534
535then files listed in a $HOME/.cvsignore are added to the list and any
536files listed in the CVSIGNORE environment variable (space delimited).
537
538Finally in each directory any files listed in the .cvsignore file in
539that directory are added to the list.
540
541dit(bf(--csum-length=LENGTH)) By default the primary checksum used in
542rsync is a very strong 16 byte MD4 checksum. In most cases you will
543find that a truncated version of this checksum is quite efficient, and
544this will decrease the size of the checksum data sent over the link,
545making things faster.
546
547You can choose the number of bytes in the truncated checksum using the
548--csum-length option. Any value less than or equal to 16 is valid.
549
550Note that if you use this option then you run the risk of ending up
551with an incorrect target file. The risk with a value of 16 is
552microscopic and can be safely ignored (the universe will probably end
553before it fails) but with smaller values the risk is higher.
554
555Current versions of rsync actually use an adaptive algorithm for the
556checksum length by default, using a 16 byte file checksum to determine
557if a 2nd pass is required with a longer block checksum. Only use this
558option if you have read the source code and know what you are doing.
559
560dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a
561scratch directory when creating temporary copies of the files
562transferred on the receiving side. The default behavior is to create
563the temporary files in the receiving directory.
564
565dit(bf(--compare-dest=DIR)) This option instructs rsync to use DIR as an
566additional directory to compare destination files against when doing
567transfers. This is useful for doing transfers to a new destination while
568leaving existing files intact, and then doing a flash-cutover when all
569files have been successfully transferred (for example by moving directories
570around and removing the old directory, although this requires also doing
571the transfer with -I to avoid skipping files that haven't changed). This
572option increases the usefulness of --partial because partially transferred
573files will remain in the new temporary destination until they have a chance
574to be completed. If DIR is a relative path, it is relative to the
575destination directory.
576
577dit(bf(-z, --compress)) With this option, rsync compresses any data from
578the source file(s) which it sends to the destination machine. This
579option is useful on slow links. The compression method used is the
580same method that gzip uses.
581
582Note this this option typically achieves better compression ratios
583that can be achieved by using a compressing remote shell, or a
584compressing transport, as it takes advantage of the implicit
585information sent for matching data blocks.
586
587dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
588and user ids rather than using user and group names and mapping them
589at both ends.
590
591By default rsync will use the user name and group name to determine
592what ownership to give files. The special uid 0 and the special group
5930 are never mapped via user/group names even if the --numeric-ids
594option is not specified.
595
596If the source system is a daemon using chroot, or if a user or group name
597does not exist on the destination system, then the numeric id from the
598source system is used instead.
599
600dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum IO
601timeout in seconds. If no data is transferred for the specified time
602then rsync will exit. The default is 0, which means no timeout.
603
604dit(bf(--daemon)) This tells rsync that it is to run as a rsync
605daemon. If standard input is a socket then rsync will assume that it
606is being run via inetd, otherwise it will detach from the current
607terminal and become a background daemon. The daemon will read the
608config file (/etc/rsyncd.conf) on each connect made by a client and
609respond to requests accordingly. See the rsyncd.conf(5) man page for more
610details.
611
612dit(bf(--address)) By default rsync will bind to the wildcard address
613when run as a daemon with the --daemon option or when connecting to a
614rsync server. The --address option allows you to specify a specific IP
615address (or hostname) to bind to. This makes virtual hosting possible
616in conjunction with the --config option.
617
618dit(bf(--config=FILE)) This specifies an alternate config file than
619the default /etc/rsyncd.conf. This is only relevant when --daemon is
620specified.
621
622dit(bf(--port=PORT)) This specifies an alternate TCP port number to use
623rather than the default port 873.
624
625dit(bf(--blocking-io)) This tells rsync to use blocking IO when launching
626a remote shell transport. If -e or --rsh are not specified or are set to
627the default "rsh", this defaults to blocking IO, otherwise it defaults to
628non-blocking IO. You may find the --blocking-io option is needed for some
629remote shells that can't handle non-blocking IO. Ssh prefers blocking IO.
630
631dit(bf(--log-format=FORMAT)) This allows you to specify exactly what the
632rsync client logs to stdout on a per-file basis. The log format is
633specified using the same format conventions as the log format option in
634rsyncd.conf.
635
636dit(bf(--stats)) This tells rsync to print a verbose set of statistics
637on the file transfer, allowing you to tell how effective the rsync
638algorithm is for your data.
639
640dit(bf(--partial)) By default, rsync will delete any partially
641transferred file if the transfer is interrupted. In some circumstances
642it is more desirable to keep partially transferred files. Using the
643--partial option tells rsync to keep the partial file which should
644make a subsequent transfer of the rest of the file much faster.
645
646dit(bf(--progress)) This option tells rsync to print information
647showing the progress of the transfer. This gives a bored user
648something to watch.
649
650This option is normally combined with -v. Using this option without
651the -v option will produce weird results on your display.
652
653dit(bf(-P)) The -P option is equivalent to --partial --progress. I
654found myself typing that combination quite often so I created an
655option to make it easier.
656
657dit(bf(--password-file)) This option allows you to provide a password
658in a file for accessing a remote rsync server. Note that this option
659is only useful when accessing a rsync server using the built in
660transport, not when using a remote shell as the transport. The file
661must not be world readable. It should contain just the password as a
662single line.
663
664dit(bf(--bwlimit=KBPS)) This option allows you to specify a maximum
665transfer rate in kilobytes per second. This option is most effective when
666using rsync with large files (several megabytes and up). Due to the nature
667of rsync transfers, blocks of data are sent, then if rsync determines the
668transfer was too fast, it will wait before sending the next data block. The
669result is an average transfer rate equalling the specified limit. A value
670of zero specifies no limit.
671
672enddit()
673
674manpagesection(EXCLUDE PATTERNS)
675
676The exclude and include patterns specified to rsync allow for flexible
677selection of which files to transfer and which files to skip.
678
679rsync builds a ordered list of include/exclude options as specified on
680the command line. When a filename is encountered, rsync checks the
681name against each exclude/include pattern in turn. The first matching
682pattern is acted on. If it is an exclude pattern, then that file is
683skipped. If it is an include pattern then that filename is not
684skipped. If no matching include/exclude pattern is found then the
685filename is not skipped.
686
687Note that when used with -r (which is implied by -a), every subcomponent of
688every path is visited from top down, so include/exclude patterns get
689applied recursively to each subcomponent.
690
691Note also that the --include and --exclude options take one pattern
692each. To add multiple patterns use the --include-from and
693--exclude-from options or multiple --include and --exclude options.
694
695The patterns can take several forms. The rules are:
696
697itemize(
698 it() if the pattern starts with a / then it is matched against the
699 start of the filename, otherwise it is matched against the end of
700 the filename. Thus "/foo" would match a file called "foo" at the base of
701 the tree. On the other hand, "foo" would match any file called "foo"
702 anywhere in the tree because the algorithm is applied recursively from
703 top down; it behaves as if each path component gets a turn at being the
704 end of the file name.
705
706 it() if the pattern ends with a / then it will only match a
707 directory, not a file, link or device.
708
709 it() if the pattern contains a wildcard character from the set
710 *?[ then expression matching is applied using the shell filename
711 matching rules. Otherwise a simple string match is used.
712
713 it() if the pattern includes a double asterisk "**" then all wildcards in
714 the pattern will match slashes, otherwise they will stop at slashes.
715
716 it() if the pattern contains a / (not counting a trailing /) then it
717 is matched against the full filename, including any leading
718 directory. If the pattern doesn't contain a / then it is matched
719 only against the final component of the filename. Again, remember
720 that the algorithm is applied recursively so "full filename" can
721 actually be any portion of a path.
722
723 it() if the pattern starts with "+ " (a plus followed by a space)
724 then it is always considered an include pattern, even if specified as
725 part of an exclude option. The "+ " part is discarded before matching.
726
727 it() if the pattern starts with "- " (a minus followed by a space)
728 then it is always considered an exclude pattern, even if specified as
729 part of an include option. The "- " part is discarded before matching.
730
731 it() if the pattern is a single exclamation mark ! then the current
732 exclude list is reset, removing all previous exclude patterns.
733)
734
735The +/- rules are most useful in exclude lists, allowing you to have a
736single exclude list that contains both include and exclude options.
737
738If you end an exclude list with --exclude '*', note that since the
739algorithm is applied recursively that unless you explicitly include
740parent directories of files you want to include then the algorithm
741will stop at the parent directories and never see the files below
742them. To include all directories, use --include '*/' before the
743--exclude '*'.
744
745Here are some exclude/include examples:
746
747itemize(
748 it() --exclude "*.o" would exclude all filenames matching *.o
749 it() --exclude "/foo" would exclude a file in the base directory called foo
750 it() --exclude "foo/" would exclude any directory called foo
751 it() --exclude "/foo/*/bar" would exclude any file called bar two
752 levels below a base directory called foo
753 it() --exclude "/foo/**/bar" would exclude any file called bar two
754 or more levels below a base directory called foo
755 it() --include "*/" --include "*.c" --exclude "*" would include all
756 directories and C source files
757 it() --include "foo/" --include "foo/bar.c" --exclude "*" would include
758 only foo/bar.c (the foo/ directory must be explicitly included or
759 it would be excluded by the "*")
760)
761
762manpagesection(DIAGNOSTICS)
763
764rsync occasionally produces error messages that may seem a little
765cryptic. The one that seems to cause the most confusion is "protocol
766version mismatch - is your shell clean?".
767
768This message is usually caused by your startup scripts or remote shell
769facility producing unwanted garbage on the stream that rsync is using
770for its transport. The way to diagnose this problem is to run your
771remote shell like this:
772
773verb(
774 rsh remotehost /bin/true > out.dat
775)
776
777then look at out.dat. If everything is working correctly then out.dat
778should be a zero length file. If you are getting the above error from
779rsync then you will probably find that out.dat contains some text or
780data. Look at the contents and try to work out what is producing
781it. The most common cause is incorrectly configured shell startup
782scripts (such as .cshrc or .profile) that contain output statements
783for non-interactive logins.
784
785If you are having trouble debugging include and exclude patterns, then
786try specifying the -vv option. At this level of verbosity rsync will
787show why each individual file is included or excluded.
788
789manpagesection(ENVIRONMENT VARIABLES)
790
791startdit()
792
793dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
794ignore patterns in .cvsignore files. See the --cvs-exclude option for
795more details.
796
797dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
798override the default shell used as the transport for rsync. This can
799be used instead of the -e option.
800
801dit(bf(RSYNC_PROXY)) The RSYNC_PROXY environment variable allows you to
802redirect your rsync client to use a web proxy when connecting to a
803rsync daemon. You should set RSYNC_PROXY to a hostname:port pair.
804
805dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
806password allows you to run authenticated rsync connections to a rsync
807daemon without user intervention. Note that this does not supply a
808password to a shell transport such as ssh.
809
810dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
811are used to determine the default username sent to a rsync server.
812
813dit(bf(HOME)) The HOME environment variable is used to find the user's
814default .cvsignore file.
815
816enddit()
817
818manpagefiles()
819
820/etc/rsyncd.conf
821
822manpageseealso()
823
824rsyncd.conf(5)
825
826manpagediagnostics()
827
828manpagebugs()
829
830times are transferred as unix time_t values
831
832file permissions, devices etc are transferred as native numerical
833values
834
835see also the comments on the --delete option
836
837Please report bugs! The rsync bug tracking system is online at
838url(http://rsync.samba.org/rsync/)(http://rsync.samba.org/rsync/)
839
840manpagesection(VERSION)
841This man page is current for version 2.0 of rsync
842
843manpagesection(CREDITS)
844
845rsync is distributed under the GNU public license. See the file
846COPYING for details.
847
848A WEB site is available at
849url(http://rsync.samba.org/)(http://rsync.samba.org/)
850
851The primary ftp site for rsync is
852url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync).
853
854We would be delighted to hear from you if you like this program.
855
856This program uses the excellent zlib compression library written by
857Jean-loup Gailly and Mark Adler.
858
859manpagesection(THANKS)
860
861Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
862and David Bell for helpful suggestions and testing of rsync. I've
863probably missed some people, my apologies if I have.
864
865
866manpageauthor()
867
868rsync was written by Andrew Tridgell and Paul Mackerras. They may be
869contacted via email at tridge@samba.org and
870Paul.Mackerras@cs.anu.edu.au
871