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