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