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