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