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