- only keep a partial file if some literal data has been transferred,
[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
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
8e987130
AT
84Note that rsync must be installed on both the source and destination
85machines.
86
41059f75
AT
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
4c3d16be
AT
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
41059f75
AT
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
c95da96a
AT
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(
196 -v, --verbose increase verbosity
197 -c, --checksum always checksum
198 -a, --archive archive mode
199 -r, --recursive recurse into directories
200 -R, --relative use relative path names
201 -b, --backup make backups (default ~ extension)
202 -u, --update update only (don't overwrite newer files)
203 -l, --links preserve soft links
204 -L, --copy-links treat soft links like regular files
205 -H, --hard-links preserve hard links
206 -p, --perms preserve permissions
207 -o, --owner preserve owner (root only)
208 -g, --group preserve group
209 -D, --devices preserve devices (root only)
210 -t, --times preserve times
211 -S, --sparse handle sparse files efficiently
212 -n, --dry-run show what would have been transferred
213 -W, --whole-file copy whole files, no incremental checks
214 -x, --one-file-system don't cross filesystem boundaries
215 -B, --block-size=SIZE checksum blocking size
216 -e, --rsh=COMMAND specify rsh replacement
217 --rsync-path=PATH specify path to rsync on the remote machine
218 -C, --cvs-exclude auto ignore files in the same way CVS does
219 --delete delete files that don't exist on the sending side
220 --partial keep partially transferred files
221 --force force deletion of directories even if not empty
222 --numeric-ids don't map uid/gid values by user/group name
223 --timeout=TIME set IO timeout in seconds
224 -I, --ignore-times don't exclude files that match length and time
225 -T --temp-dir=DIR create temporary files in directory DIR
226 -z, --compress compress file data
227 --exclude=PATTERN exclude file FILE
228 --exclude-from=PATTERN exclude files listed in FILE
229 --include=PATTERN don't exclude file FILE
230 --include-from=PATTERN don't exclude files listed in FILE
231 --suffix=SUFFIX override backup suffix
232 --version print version number
233 --daemon run as a rsync daemon
234 --config=FILE specify alternate rsyncd.conf file
235 --port=PORT specify alternate rsyncd port number
236 --stats give some file transfer stats
237 -h, --help show this help screen
238)
239
41059f75
AT
240manpageoptions()
241
242rsync uses the GNU long options package. Many of the command line
243options have two variants, one short and one long. These are shown
244below separated by commas. Some options only have a long variant.
245
246startdit()
247dit(bf(-h, --help)) Print a short help page describing the options
248available in rsync
249
250dit(bf(--version)) print the rsync version number and exit
251
252dit(bf(-v, --verbose)) This option increases the amount of information you
253are given during the transfer. By default rsync works silently. A
254single -v will give you information about what files are being
255transferred and a brief summary at the end. Two -v flags will give you
256information on what files are being skipped and slightly more
257information at the end. More than two -v flags should only be used if
258you are debugging rsync
259
260dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
261already the same length and have the same time-stamp. This option turns
262off this behavior.
263
264dit(bf(-c, --checksum)) This forces the sender to checksum all files using
265a 128-bit MD4 checksum before transfer. The checksum is then
266explicitly checked on the receiver and any files of the same name
267which already exist and have the same checksum and size on the
268receiver are skipped. This option can be quite slow.
269
5243c216 270dit(bf(-a, --archive)) This is equivalent to -rlptDg. It is a quick way
41059f75
AT
271of saying I want recursion and want to preserve everything.
272
5243c216
AT
273Note: if the user launching rsync is root then the -o option (preserve
274uid) is also implied.
275
41059f75
AT
276dit(bf(-r, --recursive)) This tells rsync to copy directories recursively
277
278dit(bf(-R, --relative)) Use relative paths. This means that the full path
279names specified on the command line are sent to the server rather than
280just the last parts of the filenames. This is particularly useful when
281you want to sent several different directories at the same time. For
282example if you used the command
283
284verb(rsync foo/bar/foo.c remote:/tmp/)
285
286then this would create a file called foo.c in /tmp/ on the remote
287machine. If instead you used
288
289verb(rsync -R foo/bar/foo.c remote:/tmp/)
290
291then a file called /tmp/foo/bar/foo.c would be created on the remote
292machine. The full path name is preserved.
293
294dit(bf(-b, --backup)) With this option preexisting destination files are
295renamed with a ~ extension as each file is transferred. You can
296control the backup suffix using the --suffix option.
297
298dit(bf(-u, --update)) This forces rsync to skip any files for which the
299destination file already exists and has a date later than the source
300file.
301
302dit(bf(-l, --links)) This tells rsync to recreate symbolic links on the
303remote system to be the same as the local system. Without this
304option all symbolic links are skipped.
305
306dit(bf(-L, --copy-links)) This tells rsync to treat symbolic links just
307like ordinary files.
308
309dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on
310the remote system to be the same as the local system. Without this
311option hard links are treated like regular files.
312
313Note that rsync can only detect hard links if both parts of the link
314are in the list of files being sent.
315
316This option can be quite slow, so only use it if you need it.
317
318dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm
319is not used and the whole file is sent as-is instead. This may be
320useful when using rsync with a local machine.
321
c95da96a
AT
322dit(bf(--partial)) By default rsync will delete any partially
323transferred file if the transfer is interrupted. In some circumstances
324it is more desirable to keep partially transferred files. Using the
325--partial option tells rsync to keep the partial file which should
326make a subsequent transfer of the rest of the file much faster.
327
41059f75
AT
328dit(bf(-p, --perms)) This option causes rsync to update the remote
329permissions to be the same as the local permissions.
330
331dit(bf(-o, --owner)) This option causes rsync to update the remote owner
332of the file to be the same as the local owner. This is only available
333to the super-user.
334
335dit(bf(-g, --group)) This option causes rsync to update the remote group
336of the file to be the same as the local group.
337
338dit(bf(-D, --devices)) This option causes rsync to transfer character and
339block device information to the remote system to recreate these
340devices. This option is only available to the super-user.
341
342dit(bf(-t, --times)) This tells rsync to transfer modification times along
343with the files and update them on the remote system
344
345dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers,
346instead it will just report the actions it would have taken.
347
348dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take
349up less space on the destination.
350
351dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem
352boundaries when recursing. This is useful for transferring the
353contents of only one filesystem.
354
355dit(bf(--delete)) This tells rsync to delete any files on the receiving
356side that aren't on the sending side. This option can be dangerous if
357used incorrectly!
358
359It is a very good idea to run first using the dry run option (-n) to
360see what files would be deleted to make sure important files aren't
361listed.
362
363rsync 1.6.4 changed the behavior of --delete to make it less
364dangerous. rsync now only scans directories on the receiving side
365that are explicitly transferred from the sending side. Only files in
366these directories are deleted.
367
368Still, it is probably easy to get burnt with this option. The moral
369of the story is to use the -n option until you get used to the
370behavior of --delete.
371
372NOTE: It also may delete files on the destination if the sending side
373can't open them or stat them. This is a bug that hopefully will be
374fixed in a future release.
375
376dit(bf(--force)) This options tells rsync to delete directories even if
377they are not empty. This applies to both the --delete option and to
378cases where rsync tries to copy a normal file but the destination
379contains a directory of the same name. Normally rsync will refuse to
380do a recursive directory deletion in such cases, by using --force
381the recursive deletion will be done.
382
383Use this option with caution!
384
385dit(bf(-B , --block_size BLOCKSIZE)) This controls the block size used in
386the rsync algorithm. See the technical report for details.
387
388dit(bf(-e, --rsh COMMAND)) This option allows you to choose an alternative
389remote shell program to use for communication between the local and
390remote copies of rsync. By default rsync will use rsh, but you may
391like to instead use ssh because of its high security.
392
393You can also choose the remote shell program using the RSYNC_RSH
394environment variable.
395
396dit(bf(--rsync-path PATH)) Use this to specify the path to the copy of
397rsync on the remote machine. Useful when its not in your path.
398
43bd68e5 399dit(bf(--exclude pattern)) This option allows you to selectively exclude
41059f75
AT
400certain files from the list of files to be transferred. This is most
401useful in combination with a recursive transfer.
402
41059f75
AT
403You may use as many --exclude options on the command line as you like
404to build up the list of files to exclude.
405
43bd68e5
AT
406See the section of exclude patterns for information on the syntax of
407this option.
41059f75
AT
408
409dit(bf(--exclude-from FILE)) This option is similar to the --exclude
410option, but instead it adds all filenames listed in the file FILE to
411the exclude list.
412
43bd68e5
AT
413dit(bf(--include pattern)) This option tells rsync to not exclude the
414specified pattern of filenames. This is useful as it allows you to
415build up quite complex exclude/include rules.
416
417See the section of exclude patterns for information on the syntax of
418this option.
419
420dit(bf(--include-from FILE)) This specifies a list of include patterns
421from a file.
422
41059f75
AT
423dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
424broad range of files that you often don't want to transfer between
425systems. It uses the same algorithm that CVS uses to determine if
426a file should be ignored.
427
428The exclude list is initialized to:
429
430quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state
431.nse_depinfo *~ #* .#* ,* *.old *.bak *.BAK *.orig *.rej .del-*
432*.a *.o *.obj *.so *.Z *.elc *.ln core)
433
434then files listed in a $HOME/.cvsignore are added to the list and any
435files listed in the CVSIGNORE environment variable (space delimited).
436
437Finally in each directory any files listed in the .cvsignore file in
438that directory are added to the list.
439
440dit(bf(--suffix SUFFIX)) This option allows you to override the default
441backup suffix used with the -b option. The default is a ~.
442
443dit(bf(--csum-length LENGTH)) By default the primary checksum used in
444rsync is a very strong 16 byte MD4 checksum. In most cases you will
445find that a truncated version of this checksum is quite efficient, and
446this will decrease the size of the checksum data sent over the link,
de2fd20e 447making things faster.
41059f75
AT
448
449You can choose the number of bytes in the truncated checksum using the
450--csum-length option. Any value less than or equal to 16 is valid.
451
452Note that if you use this option then you run the risk of ending up
453with an incorrect target file. The risk with a value of 16 is
454microscopic and can be safely ignored (the universe will probably end
455before it fails) but with smaller values the risk is higher.
456
de2fd20e
AT
457Current versions of rsync actually use an adaptive algorithm for the
458checksum length by default, using a 16 byte file checksum to determine
459if a 2nd pass is required with a longer block checksum. Only use this
460option if you have read the source code and know what you are doing.
461
41059f75
AT
462dit(bf(-T, --temp-dir DIR)) This options instructs rsync to use DIR as a
463scratch directory when creating a temporary copies of the files
464transferred on the receiving side. The default behavior is to create
465the temporary files in the receiving directory.
466
467dit(bf(-z, --compress)) With this option, rsync compresses any data from
468the source file(s) which it sends to the destination machine. This
469option is useful on slow links. The compression method used is the
470same method that gzip uses.
471
472Note this this option typically achieves better compression ratios
473that can be achieved by using a compressing remote shell, or a
474compressing transport, as it takes advantage of the implicit
475information sent for matching data blocks.
476
477dit(bf(--numeric-ids)) With this option rsync will transfer numeric group
478and user ids rather than using user and group names and mapping them
479at both ends.
480
481By default rsync will use the user name and group name to determine
482what ownership to give files. The special uid 0 and the special group
4830 and never mapped via user/group names even if the --numeric-ids
484option is not specified.
485
486If a user or group name does not exist on the destination system then
487the numeric id from the source system is used instead.
488
de2fd20e
AT
489dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum IO
490timeout in seconds. If no data is transferred for the specified time
491then rsync will exit. The default is 0, which means no timeout.
41059f75
AT
492
493dit(bf(--daemon)) This tells rsync that it is to run as a rsync
494daemon. If standard input is a socket then rsync will assume that it
495is being run via inetd, otherwise it will detach from the current
5315b793 496terminal and become a background daemon. The daemon will read the
41059f75
AT
497config file (/etc/rsyncd.conf) on each connect made by a client and
498respond to requests accordingly. See the rsyncd.conf(5) man page for more
499details.
500
501dit(bf(--config FILE)) This specifies an alternate config file than
5315b793 502the default /etc/rsyncd.conf. This is only relevant when --daemon is
41059f75
AT
503specified.
504
505dit(bf(--port PORT)) This specifies an alternate TCP port number to use
506rather than the default port 873.
507
b72f24c7
AT
508dit(bf(--stats)) This tells rsync to print a verbose set of statistics
509on the file transfer, allowing you to tell how effective the rsync
56cdbccb
AT
510algorithm is for your data. This option only works in conjunction with
511the -v (verbose) option.
b72f24c7 512
41059f75
AT
513enddit()
514
43bd68e5
AT
515manpagesection(EXCLUDE PATTERNS)
516
517The exclude and include patterns specified to rsync allow for flexible
518selection of what files to transfer and what files to skip.
519
520rsync build a ordered list of include/exclude options as specified on
521the command line. When a filename is encountered rsync then checks the
522name against each exclude/include pattern in turn. The first matching
523pattern is acted on. If it is an exclude pattern than that file is
524skipped. If it is an include pattern then that filename is not
525skipped. If no matching include/exclude pattern is found then the
526filename is not skipped.
527
528The patterns themselves can take several forms. The rules are:
529
530itemize(
531 it() if the pattern starts with a / then it is matched against the
532 start of the filename, otherwise it is matched against the end of
533 the filename. Thus /foo would match a file called foo
534 at the base of the tree whereas foo would match any file
535 called foo anywhere in the tree.
536
537 it() if the pattern ends with a / then it will only match a
538 directory, not a file, link or device.
539
540 it() if the pattern contains a wildcard character from the set
541 *?[ then regular expression matching is applied using the
542 normal shell filename matching rules. Otherwise a simple string
543 match is used.
544
545 it() if the pattern contains a / (not counting a trailing /) then it
546 is matched against the full filename, including any leading
547 directory. If the pattern doesn't contain a / then it is matched
548 only against the final component of the filename.
549
550 it() if the pattern starts with "+ " (a plus followed by a space)
551 then it is always considered a include pattern, even if specified as
552 part of an exclude option. The "+ " part is discarded before matching.
553
554 it() if the pattern starts with "- " (a minus followed by a space)
555 then it is always considered a exclude pattern, even if specified as
556 part of an include option. The "- " part is discarded before matching.
de2fd20e
AT
557
558 it() if the pattern is a single exclamation mark ! then the current
559 exclude list is reset, removing all previous exclude patterns.
43bd68e5
AT
560)
561
562The +/- rules are most useful in exclude lists, allowing you to have a
563single exclude list that contains both include and exclude options.
564
565Here are some examples:
566
567itemize(
568 it() --exclude "*.o" would exclude all filenames matching *.o
569 it() --exclude "/foo" would exclude a file in the base directory called foo
570 it() --exclude "foo/" would exclude any directory called foo
571 it() --include "*/" --include "*.c" --exclude "*" would include all
572 directories and C source files.
573)
574
de2fd20e
AT
575manpagesection(ENVIRONMENT VARIABLES)
576
577startdit()
578
579dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any
580ignore patterns in .cvsignore files. See the --cvs-exclude option for
581more details.
582
583dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to
584override the default shell used as the transport for rsync. This can
585be used instead of the -e option.
586
587dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required
588password allows you to run authenticated rsync connections to a rsync
589daemon without user intervention. Note that this does not supply a
590password to a shell transport such as ssh.
591
592dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables
593are used to determine the default username sent to a rsync server.
594
595dit(bf(HOME)) The HOME environment variable is used to find the users
596default .cvsignore file.
597
598enddit()
599
41059f75
AT
600manpagefiles()
601
602/etc/rsyncd.conf
603
604manpageseealso()
605
606rsyncd.conf(5)
607
608manpagediagnostics()
609
610manpagebugs()
611
612times are transferred as unix time_t values
613
614file permissions, devices etc are transferred as native numerical
615values
616
a87b3b2a 617see also the comments on the --delete option
41059f75
AT
618
619Please report bugs! The rsync bug tracking system is online at
620url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
621
622manpagesection(VERSION)
623This man page is current for version 2.0 of rsync
624
625manpagesection(CREDITS)
626
627rsync is distributed under the GNU public license. See the file
628COPYING for details.
629
630The primary ftp site for rsync is
631url(ftp://samba.anu.edu.au/pub/rsync)(ftp://samba.anu.edu.au/pub/rsync).
632
633A WEB site is available at
634url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
635
636We would be delighted to hear from you if you like this program.
637
638This program uses the zlib compression library written by Jean-loup
639Gailly and Mark Adler.
640
641manpagesection(THANKS)
642
643Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell
644and David Bell for helpful suggestions and testing of rsync. I've
645probably missed some people, my apologies if I have.
646
647
648manpageauthor()
649
650rsync was written by Andrew Tridgell and Paul Mackerras. They may be
651contacted via email at tridge@samba.anu.edu.au and
652Paul.Mackerras@cs.anu.edu.au
653