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