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