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