Fixed bug introduced by calling do_open() for O_RDONLY files. Changed it
[rsync/rsync.git] / rsync.yo
... / ...
CommitLineData
1mailto(rsync-bugs@samba.org)
2manpage(rsync)(1)(1 Mar 1999)()()
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(
219Usage: rsync [OPTION]... SRC [SRC]... [USER@]HOST:DEST
220 or rsync [OPTION]... [USER@]HOST:SRC DEST
221 or rsync [OPTION]... SRC [SRC]... DEST
222 or rsync [OPTION]... [USER@]HOST::SRC [DEST]
223 or rsync [OPTION]... SRC [SRC]... [USER@]HOST::DEST
224 or rsync [OPTION]... rsync://[USER@]HOST[:PORT]/SRC [DEST]
225SRC on single-colon remote HOST will be expanded by remote shell
226SRC on server remote HOST may contain shell wildcards or multiple
227 sources separated by space as long as they have same top-level
228
229Options
230 -v, --verbose increase verbosity
231 -q, --quiet decrease verbosity
232 -c, --checksum always checksum
233 -a, --archive archive mode
234 -r, --recursive recurse into directories
235 -R, --relative use relative path names
236 -b, --backup make backups (default ~ suffix)
237 --suffix=SUFFIX override backup suffix
238 -u, --update update only (don't overwrite newer files)
239 -l, --links preserve soft links
240 -L, --copy-links treat soft links like regular files
241 --copy-unsafe-links copy links outside the source tree
242 --safe-links ignore links outside the destination tree
243 -H, --hard-links preserve hard links
244 -p, --perms preserve permissions
245 -o, --owner preserve owner (root only)
246 -g, --group preserve group
247 -D, --devices preserve devices (root only)
248 -t, --times preserve times
249 -S, --sparse handle sparse files efficiently
250 -n, --dry-run show what would have been transferred
251 -W, --whole-file copy whole files, no incremental checks
252 -x, --one-file-system don't cross filesystem boundaries
253 -B, --block-size=SIZE checksum blocking size (default 700)
254 -e, --rsh=COMMAND specify rsh replacement
255 --rsync-path=PATH specify path to rsync on the remote machine
256 -C, --cvs-exclude auto ignore files in the same way CVS does
257 --delete delete files that don't exist on the sending side
258 --delete-excluded also delete excluded files on the receiving side
259 --partial keep partially transferred files
260 --force force deletion of directories even if not empty
261 --numeric-ids don't map uid/gid values by user/group name
262 --timeout=TIME set IO timeout in seconds
263 -I, --ignore-times don't exclude files that match length and time
264 --size-only only use file size when determining if a file should be transferred
265 -T --temp-dir=DIR create temporary files in directory DIR
266 --compare-dest=DIR also compare destination files relative to DIR
267 -P equivalent to --partial --progress
268 -z, --compress compress file data
269 --exclude=PATTERN exclude files matching PATTERN
270 --exclude-from=FILE exclude patterns listed in FILE
271 --include=PATTERN don't exclude files matching PATTERN
272 --include-from=FILE don't exclude patterns listed in FILE
273 --version print version number
274 --daemon run as a rsync daemon
275 --address bind to the specified address
276 --config=FILE specify alternate rsyncd.conf file
277 --port=PORT specify alternate rsyncd port number
278 --stats give some file transfer stats
279 --progress show progress during transfer
280 --log-format=FORMAT log file transfers using specified format
281 --password-file=FILE get password from FILE
282 -h, --help show this help screen
283)
284
285manpageoptions()
286
287rsync uses the GNU long options package. Many of the command line
288options have two variants, one short and one long. These are shown
289below, separated by commas. Some options only have a long variant.
290The '=' for options that take a parameter is optional; whitespace
291can be used instead.
292
293startdit()
294dit(bf(-h, --help)) Print a short help page describing the options
295available in rsync
296
297dit(bf(--version)) print the rsync version number and exit
298
299dit(bf(-v, --verbose)) This option increases the amount of information you
300are given during the transfer. By default, rsync works silently. A
301single -v will give you information about what files are being
302transferred and a brief summary at the end. Two -v flags will give you
303information on what files are being skipped and slightly more
304information at the end. More than two -v flags should only be used if
305you are debugging rsync.
306
307dit(bf(-q, --quiet)) This option decreases the amount of information you
308are given during the transfer, notably suppressing information messages
309from the remote server. This flag is useful when invoking rsync from
310cron.
311
312dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
313already the same length and have the same time-stamp. This option turns
314off this behavior.
315
316dit(bf(-I, --size-only)) Normally rsync will skip any files that are
317already the same length and have the same time-stamp. With the
318--size-only option files will be skipped if they have the same size,
319regardless of timestamp. This is useful when starting to use rsync
320after using another mirroring system which may not preserve timestamps
321exactly.
322
323dit(bf(-c, --checksum)) This forces the sender to checksum all files using
324a 128-bit MD4 checksum before transfer. The checksum is then
325explicitly checked on the receiver and any files of the same name
326which already exist and have the same checksum and size on the
327receiver are skipped. This option can be quite slow.
328
329dit(bf(-a, --archive)) This is equivalent to -rlptg. It is a quick way
330of saying you want recursion and want to preserve everything.
331
332Note: if the user launching rsync is root then the -o (preserve
333uid) and -D (preserve devices) options are also implied.
334
335dit(bf(-r, --recursive)) This tells rsync to copy directories
336recursively. If you don't specify this then rsync won't copy
337directories at all.
338
339dit(bf(-R, --relative)) Use relative paths. This means that the full path
340names specified on the command line are sent to the server rather than
341just the last parts of the filenames. This is particularly useful when
342you want to send several different directories at the same time. For
343example, if you used the command
344
345verb(rsync foo/bar/foo.c remote:/tmp/)
346
347then this would create a file called foo.c in /tmp/ on the remote
348machine. If instead you used
349
350verb(rsync -R foo/bar/foo.c remote:/tmp/)
351
352then a file called /tmp/foo/bar/foo.c would be created on the remote
353machine. The full path name is preserved.
354
355dit(bf(-b, --backup)) With this option preexisting destination files are
356renamed with a ~ extension as each file is transferred. You can
357control the backup suffix using the --suffix option.
358
359dit(bf(--suffix=SUFFIX)) This option allows you to override the default
360backup suffix used with the -b option. The default is a ~.
361
362dit(bf(-u, --update)) This forces rsync to skip any files for which the
363destination file already exists and has a date later than the source
364file.
365
366dit(bf(-l, --links)) This tells rsync to recreate symbolic links on the
367remote system to be the same as the local system. Without this
368option, all symbolic links are skipped.
369
370dit(bf(-L, --copy-links)) This tells rsync to treat symbolic links just
371like ordinary files.
372
373dit(bf(--copy-unsafe-links)) This tells rsync to treat symbolic links that
374point outside the source tree like ordinary files. Absolute symlinks are
375also treated like ordinary files, and so are any symlinks in the source
376path itself when --relative is used.
377
378dit(bf(--safe-links)) This tells rsync to ignore any symbolic links
379which point outside the destination tree. All absolute symlinks are
380also ignored. Using this option in conjunction with --relative may
381give unexpected results.
382
383dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on
384the remote system to be the same as the local system. Without this
385option hard links are treated like regular files.
386
387Note that rsync can only detect hard links if both parts of the link
388are in the list of files being sent.
389
390This option can be quite slow, so only use it if you need it.
391
392dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
393is not used and the whole file is sent as-is instead. This may be
394useful when using rsync with a local machine.
395
396dit(bf(-p, --perms)) This option causes rsync to update the remote
397permissions to be the same as the local permissions.
398
399dit(bf(-o, --owner)) This option causes rsync to update the remote owner
400of the file to be the same as the local owner. This is only available
401to the super-user. Note that if the source system is a daemon using chroot,
402the --numeric-ids option is implied because the source system cannot get
403access to the usernames.
404
405dit(bf(-g, --group)) This option causes rsync to update the remote group
406of the file to be the same as the local group. If the receving system is
407not running as the super-user, only groups that the receiver is a member of
408will be preserved (by group name, not group id number).
409
410dit(bf(-D, --devices)) This option causes rsync to transfer character and
411block device information to the remote system to recreate these
412devices. This option is only available to the super-user.
413
414dit(bf(-t, --times)) This tells rsync to transfer modification times along
415with the files and update them on the remote system. Note that if this
416option is not used, the optimization that excludes files that have not been
417modified cannot be effective; in other words, a missing -t or -a will
418cause the next transfer to behave as if it used -I, and all files will have
419their checksums compared and show up in log messages even if they haven't
420changed.
421
422dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers,
423instead it will just report the actions it would have taken.
424
425dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
426up less space on the destination.
427
428NOTE: Don't use this option when the destination is a Solaris "tmpfs"
429filesystem. It doesn't seem to handle seeks over null regions
430correctly and ends up corrupting the files.
431
432dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem
433boundaries when recursing. This is useful for transferring the
434contents of only one filesystem.
435
436dit(bf(--delete)) This tells rsync to delete any files on the receiving
437side that aren't on the sending side. Files that are excluded from
438transfer are excluded from being deleted unless you use --delete-excluded.
439
440This option has no effect if directory recursion is not selected.
441
442This option can be dangerous if used incorrectly! It is a very good idea
443to run first using the dry run option (-n) to see what files would be
444deleted to make sure important files aren't listed.
445
446If the sending side detects any IO errors then the deletion of any
447files at the destination will be automatically disabled. This is to
448prevent temporary filesystem failures (such as NFS errors) on the
449sending side causing a massive deletion of files on the
450destination.
451
452dit(bf(--delete-excluded)) In addition to deleting the files on the
453receiving side that are not on the sending side, this tells rsync to also
454delete any files on the receiving side that are excluded (see --exclude).
455
456dit(bf(--force)) This options tells rsync to delete directories even if
457they are not empty. This applies to both the --delete option and to
458cases where rsync tries to copy a normal file but the destination
459contains a directory of the same name.
460
461Since this option was added, deletions were reordered to be done depth-first
462so it is hardly ever needed anymore except in very obscure cases.
463
464dit(bf(-B , --block_size=BLOCKSIZE)) This controls the block size used in
465the rsync algorithm. See the technical report for details.
466
467dit(bf(-e, --rsh=COMMAND)) This option allows you to choose an alternative
468remote shell program to use for communication between the local and
469remote copies of rsync. By default, rsync will use rsh, but you may
470like to instead use ssh because of its high security.
471
472You can also choose the remote shell program using the RSYNC_RSH
473environment variable.
474
475dit(bf(--rsync-path=PATH)) Use this to specify the path to the copy of
476rsync on the remote machine. Useful when it's not in your path. Note
477that this is the full path to the binary, not just the directory that
478the binary is in.
479
480dit(bf(--exclude=PATTERN)) This option allows you to selectively exclude
481certain files from the list of files to be transferred. This is most
482useful in combination with a recursive transfer.
483
484You may use as many --exclude options on the command line as you like
485to build up the list of files to exclude.
486
487See the section on exclude patterns for information on the syntax of
488this option.
489
490dit(bf(--exclude-from=FILE)) This option is similar to the --exclude
491option, but instead it adds all filenames listed in the file FILE to
492the exclude list. Blank lines in FILE and lines starting with ';' or '#'
493are ignored.
494
495dit(bf(--include=PATTERN)) This option tells rsync to not exclude the
496specified pattern of filenames. This is useful as it allows you to
497build up quite complex exclude/include rules.
498
499See the section of exclude patterns for information on the syntax of
500this option.
501
502dit(bf(--include-from=FILE)) This specifies a list of include patterns
503from a file.
504
505dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
506broad range of files that you often don't want to transfer between
507systems. It uses the same algorithm that CVS uses to determine if
508a file should be ignored.
509
510The exclude list is initialized to:
511
512quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
513.nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-*
514*.a *.o *.obj *.so *.Z *.elc *.ln core)
515
516then files listed in a $HOME/.cvsignore are added to the list and any
517files listed in the CVSIGNORE environment variable (space delimited).
518
519Finally in each directory any files listed in the .cvsignore file in
520that directory are added to the list.
521
522dit(bf(--csum-length=LENGTH)) By default the primary checksum used in
523rsync is a very strong 16 byte MD4 checksum. In most cases you will
524find that a truncated version of this checksum is quite efficient, and
525this will decrease the size of the checksum data sent over the link,
526making things faster.
527
528You can choose the number of bytes in the truncated checksum using the
529--csum-length option. Any value less than or equal to 16 is valid.
530
531Note that if you use this option then you run the risk of ending up
532with an incorrect target file. The risk with a value of 16 is
533microscopic and can be safely ignored (the universe will probably end
534before it fails) but with smaller values the risk is higher.
535
536Current versions of rsync actually use an adaptive algorithm for the
537checksum length by default, using a 16 byte file checksum to determine
538if a 2nd pass is required with a longer block checksum. Only use this
539option if you have read the source code and know what you are doing.
540
541dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a
542scratch directory when creating temporary copies of the files
543transferred on the receiving side. The default behavior is to create
544the temporary files in the receiving directory.
545
546dit(bf(--compare-dest=DIR)) This option instructs rsync to use DIR as an
547additional directory to compare destination files against when doing
548transfers. This is useful for doing transfers to a new destination while
549leaving existing files intact, and then doing a flash-cutover when all
550files have been successfully transferred (for example by moving directories
551around and removing the old directory, although this requires also doing
552the transfer with -I to avoid skipping files that haven't changed). This
553option increases the usefulness of --partial because partially transferred
554files will remain in the new temporary destination until they have a chance
555to be completed. If DIR is a relative path, it is relative to the
556destination directory.
557
558dit(bf(-z, --compress)) With this option, rsync compresses any data from
559the source file(s) which it sends to the destination machine. This
560option is useful on slow links. The compression method used is the
561same method that gzip uses.
562
563Note this this option typically achieves better compression ratios
564that can be achieved by using a compressing remote shell, or a
565compressing transport, as it takes advantage of the implicit
566information sent for matching data blocks.
567
568dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
569and user ids rather than using user and group names and mapping them
570at both ends.
571
572By default rsync will use the user name and group name to determine
573what ownership to give files. The special uid 0 and the special group
5740 are never mapped via user/group names even if the --numeric-ids
575option is not specified.
576
577If the source system is a daemon using chroot, or if a user or group name
578does not exist on the destination system, then the numeric id from the
579source system is used instead.
580
581dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum IO
582timeout in seconds. If no data is transferred for the specified time
583then rsync will exit. The default is 0, which means no timeout.
584
585dit(bf(--daemon)) This tells rsync that it is to run as a rsync
586daemon. If standard input is a socket then rsync will assume that it
587is being run via inetd, otherwise it will detach from the current
588terminal and become a background daemon. The daemon will read the
589config file (/etc/rsyncd.conf) on each connect made by a client and
590respond to requests accordingly. See the rsyncd.conf(5) man page for more
591details.
592
593dit(bf(--address)) By default rsync will bind to the wildcard address
594when run as a daemon with the --daemon option. The --address option
595allows you to specify a specific IP address (or hostname) to bind
596to. This makes virtual hosting possible in conjunction with the
597--config option.
598
599dit(bf(--config=FILE)) This specifies an alternate config file than
600the default /etc/rsyncd.conf. This is only relevant when --daemon is
601specified.
602
603dit(bf(--port=PORT)) This specifies an alternate TCP port number to use
604rather than the default port 873.
605
606dit(bf(--log-format=FORMAT)) This allows you to specify exactly what the
607rsync client logs to stdout on a per-file basis. The log format is
608specified using the same format conventions as the log format option in
609rsyncd.conf.
610
611dit(bf(--stats)) This tells rsync to print a verbose set of statistics
612on the file transfer, allowing you to tell how effective the rsync
613algorithm is for your data.
614
615dit(bf(--partial)) By default, rsync will delete any partially
616transferred file if the transfer is interrupted. In some circumstances
617it is more desirable to keep partially transferred files. Using the
618--partial option tells rsync to keep the partial file which should
619make a subsequent transfer of the rest of the file much faster.
620
621dit(bf(--progress)) This option tells rsync to print information
622showing the progress of the transfer. This gives a bored user
623something to watch.
624
625This option is normally combined with -v. Using this option without
626the -v option will produce weird results on your display.
627
628dit(bf(-P)) The -P option is equivalent to --partial --progress. I
629found myself typing that combination quite often so I created an
630option to make it easier.
631
632dit(bf(--password-file)) This option allows you to provide a password
633in a file for accessing a remote rsync server. Note that this option
634is only useful when accessing a rsync server using the built in
635transport, not when using a remote shell as the transport. The file
636must not be world readable.
637
638enddit()
639
640manpagesection(EXCLUDE PATTERNS)
641
642The exclude and include patterns specified to rsync allow for flexible
643selection of which files to transfer and which files to skip.
644
645rsync builds a ordered list of include/exclude options as specified on
646the command line. When a filename is encountered, rsync checks the
647name against each exclude/include pattern in turn. The first matching
648pattern is acted on. If it is an exclude pattern than that file is
649skipped. If it is an include pattern then that filename is not
650skipped. If no matching include/exclude pattern is found then the
651filename is not skipped.
652
653The patterns can take several forms. The rules are:
654
655itemize(
656 it() if the pattern starts with a / then it is matched against the
657 start of the filename, otherwise it is matched against the end of
658 the filename. Thus /foo would match a file called foo
659 at the base of the tree whereas foo would match any file
660 called foo anywhere in the tree.
661
662 it() if the pattern ends with a / then it will only match a
663 directory, not a file, link or device.
664
665 it() if the pattern contains a wildcard character from the set
666 *?[ then expression matching is applied using the shell filename
667 matching rules. Otherwise a simple string match is used.
668
669 it() if the pattern contains a / (not counting a trailing /) then it
670 is matched against the full filename, including any leading
671 directory. If the pattern doesn't contain a / then it is matched
672 only against the final component of the filename. Furthermore, if
673 the pattern includes a double asterisk "**" then all wildcards in
674 the pattern will match slashes, otherwise they will stop at slashes.
675
676 it() if the pattern starts with "+ " (a plus followed by a space)
677 then it is always considered an include pattern, even if specified as
678 part of an exclude option. The "+ " part is discarded before matching.
679
680 it() if the pattern starts with "- " (a minus followed by a space)
681 then it is always considered an exclude pattern, even if specified as
682 part of an include option. The "- " part is discarded before matching.
683
684 it() if the pattern is a single exclamation mark ! then the current
685 exclude list is reset, removing all previous exclude patterns.
686)
687
688The +/- rules are most useful in exclude lists, allowing you to have a
689single exclude list that contains both include and exclude options.
690
691Here are some examples:
692
693itemize(
694 it() --exclude "*.o" would exclude all filenames matching *.o
695 it() --exclude "/foo" would exclude a file in the base directory called foo
696 it() --exclude "foo/" would exclude any directory called foo
697 it() --exclude "/foo/*/bar" would exclude any file called bar two
698 levels below a base directory called foo
699 it() --exclude "/foo/**/bar" would exclude any file called bar two
700 or more levels below a base directory called foo
701 it() --include "*/" --include "*.c" --exclude "*" would include all
702 directories and C source files
703 it() --include "foo/" --include "foo/bar.c" --exclude "*" would include
704 only foo/bar.c (the foo/ directory must be explicitly included or
705 it would be excluded by the "*")
706)
707
708manpagesection(DIAGNOSTICS)
709
710rsync occasionally produces error messages that may seem a little
711cryptic. The one that seems to cause the most confusion is "protocol
712version mismatch - is your shell clean?".
713
714This message is usually caused by your startup scripts or remote shell
715facility producing unwanted garbage on the stream that rsync is using
716for its transport. The way to diagnose this problem is to run your
717remote shell like this:
718
719verb(
720 rsh remotehost /bin/true > out.dat
721)
722
723then look at out.dat. If everything is working correctly then out.dat
724should be a zero length file. If you are getting the above error from
725rsync then you will probably find that out.dat contains some text or
726data. Look at the contents and try to work out what is producing
727it. The most common cause is incorrectly configured shell startup
728scripts (such as .cshrc or .profile) that contain output statements
729for non-interactive logins.
730
731manpagesection(ENVIRONMENT VARIABLES)
732
733startdit()
734
735dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
736ignore patterns in .cvsignore files. See the --cvs-exclude option for
737more details.
738
739dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
740override the default shell used as the transport for rsync. This can
741be used instead of the -e option.
742
743dit(bf(RSYNC_PROXY)) The RSYNC_PROXY environment variable allows you to
744redirect your rsync client to use a web proxy when connecting to a
745rsync daemon. You should set RSYNC_PROXY to a hostname:port pair.
746
747dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
748password allows you to run authenticated rsync connections to a rsync
749daemon without user intervention. Note that this does not supply a
750password to a shell transport such as ssh.
751
752dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
753are used to determine the default username sent to a rsync server.
754
755dit(bf(HOME)) The HOME environment variable is used to find the user's
756default .cvsignore file.
757
758enddit()
759
760manpagefiles()
761
762/etc/rsyncd.conf
763
764manpageseealso()
765
766rsyncd.conf(5)
767
768manpagediagnostics()
769
770manpagebugs()
771
772times are transferred as unix time_t values
773
774file permissions, devices etc are transferred as native numerical
775values
776
777see also the comments on the --delete option
778
779Please report bugs! The rsync bug tracking system is online at
780url(http://rsync.samba.org/rsync/)(http://rsync.samba.org/rsync/)
781
782manpagesection(VERSION)
783This man page is current for version 2.0 of rsync
784
785manpagesection(CREDITS)
786
787rsync is distributed under the GNU public license. See the file
788COPYING for details.
789
790A WEB site is available at
791url(http://rsync.samba.org/)(http://rsync.samba.org/)
792
793The primary ftp site for rsync is
794url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync).
795
796We would be delighted to hear from you if you like this program.
797
798This program uses the excellent zlib compression library written by
799Jean-loup Gailly and Mark Adler.
800
801manpagesection(THANKS)
802
803Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
804and David Bell for helpful suggestions and testing of rsync. I've
805probably missed some people, my apologies if I have.
806
807
808manpageauthor()
809
810rsync was written by Andrew Tridgell and Paul Mackerras. They may be
811contacted via email at tridge@samba.org and
812Paul.Mackerras@cs.anu.edu.au
813