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