X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/e2559dbedc3999482ebcaa66696cc4dffd5430fa..c53217a2b861ff7453cd35fcc35f2e79df419c4d:/rsync.yo diff --git a/rsync.yo b/rsync.yo index ef11ea47..07588b1b 100644 --- a/rsync.yo +++ b/rsync.yo @@ -35,7 +35,7 @@ itemize( it() support for copying links, devices, owners, groups and permissions it() exclude and exclude-from options similar to GNU tar it() a CVS exclude mode for ignoring the same files that CVS would ignore - it() can use any transparent remote shell, including rsh or ssh + it() can use any transparent remote shell, including ssh or rsh it() does not require root privileges it() pipelining of file transfers to minimize latency costs it() support for anonymous or authenticated rsync servers (ideal for @@ -51,8 +51,8 @@ itemize( source nor destination path contains a : separator it() for copying from the local machine to a remote machine using - a remote shell program as the transport (such as rsh or - ssh). This is invoked when the destination path contains a + a remote shell program as the transport (such as ssh or + rsh). This is invoked when the destination path contains a single : separator. it() for copying from a remote machine to the local machine @@ -93,9 +93,9 @@ See the file README for installation instructions. Once installed, you can use rsync to any machine that you can access via a remote shell (as well as some that you can access using the rsync -daemon-mode protocol). For remote transfers, rsync typically uses rsh +daemon-mode protocol). For remote transfers, a modern rsync uses ssh for its communications, but it may have been configured to use a -different remote shell by default, such as ssh. +different remote shell by default, such as rsh or remsh. You can also specify any remote shell you like, either by using the -e command line option, or by setting the RSYNC_RSH environment variable. @@ -115,7 +115,7 @@ Perhaps the best way to explain the syntax is some examples: quote(rsync *.c foo:src/) -this would transfer all files matching the pattern *.c from the +This would transfer all files matching the pattern *.c from the current directory to the directory src on the machine foo. If any of the files already exist on the remote system then the rsync remote-update protocol is used to update the file by sending only the @@ -123,7 +123,7 @@ differences. See the tech report for details. quote(rsync -avz foo:src/bar /data/tmp) -this would recursively transfer all files from the directory src/bar on the +This would recursively transfer all files from the directory src/bar on the machine foo into the /data/tmp/bar directory on the local machine. The files are transferred in "archive" mode, which ensures that symbolic links, devices, attributes, permissions, ownerships etc are preserved @@ -132,12 +132,17 @@ size of data portions of the transfer. quote(rsync -avz foo:src/bar/ /data/tmp) -a trailing slash on the source changes this behavior to transfer -all files from the directory src/bar on the machine foo into the -/data/tmp/. A trailing / on a source name means "copy the -contents of this directory". Without a trailing slash it means "copy -the directory". This difference becomes particularly important when -using the --delete option. +A trailing slash on the source changes this behavior to avoid creating an +additional directory level at the destination. You can think of a trailing +/ on a source as meaning "copy the contents of this directory" as opposed +to "copy the directory by name", but in both cases the attributes of the +containing directory are transferred to the containing directory on the +destination. In other words, each of the following commands copies the +files in the same way, including their setting of the attributes of +/dest/foo: + +quote(rsync -avz /src/foo /dest) +quote(rsync -avz /src/foo/ /dest/foo) You can also use rsync in local-only mode, where both the source and destination don't have a ':' in the name. In this case it behaves like @@ -145,7 +150,7 @@ an improved copy command. quote(rsync somehost.mydomain.com::) -this would list all the anonymous rsync modules available on the host +This would list all the anonymous rsync modules available on the host somehost.mydomain.com. (See the following section for more details.) @@ -189,8 +194,8 @@ users. On those systems using --password-file is recommended. manpagesection(CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM) It is sometimes useful to be able to set up file transfers using rsync -server capabilities on the remote machine, while still using rsh or -ssh for transport. This is especially useful when you want to connect +server capabilities on the remote machine, while still using ssh or +rsh for transport. This is especially useful when you want to connect to a remote machine via ssh (for encryption or to get through a firewall), but you still want to have access to the rsync server features (see RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM, @@ -229,18 +234,8 @@ user is root (e.g. chroot, setuid/setgid, etc.). There is no need to configure inetd or the services map to include the rsync server port if you run an rsync server only via a remote shell program. -To run an rsync server out of a single-use ssh key, use the -"command=em(COMMAND)" syntax in the remote user's -authorized_keys entry, where command would be - -quote(rsync --server --daemon .) - -NOTE: rsync's argument parsing expects the trailing ".", so make sure -that it's there. If you want to use a rsyncd.conf(5)-style -configuration file other than the default, you can added a ---config option to the em(command): - -quote(rsync --server --daemon --config=em(file) .) +To run an rsync server out of a single-use ssh key, see this section +in the rsyncd.conf(5) man page. manpagesection(EXAMPLES) @@ -603,8 +598,8 @@ the rsync algorithm. See the technical report for details. dit(bf(-e, --rsh=COMMAND)) This option allows you to choose an alternative remote shell program to use for communication between the local and -remote copies of rsync. Typically, rsync is configured to use rsh by -default, but you may prefer to use ssh because of its high security. +remote copies of rsync. Typically, rsync is configured to use ssh by +default, but you may prefer to use rsh on a local network. If this option is used with bf([user@]host::module/path), then the remote shell em(COMMMAND) will be used to run an rsync server on the @@ -805,11 +800,10 @@ dit(bf(--port=PORT)) This specifies an alternate TCP port number to use rather than the default port 873. dit(bf(--blocking-io)) This tells rsync to use blocking IO when launching -a remote shell transport. If -e or --rsh are not specified or are set to -the default "rsh", this defaults to blocking IO, otherwise it defaults to -non-blocking IO. You may find the --blocking-io option is needed for some -remote shells that can't handle non-blocking IO. (Note that ssh prefers -non-blocking IO.) +a remote shell transport. If the remote shell is either rsh or remsh, +rsync defaults to using +blocking IO, otherwise it defaults to using non-blocking IO. (Note that +ssh prefers non-blocking IO.) dit(bf(--no-blocking-io)) Turn off --blocking-io, for use when it is the default. @@ -1010,11 +1004,11 @@ once, instead of sending the same data to every host individually. Example: verb( -$ rsync --write_batch=pfx -a /source/dir/ /adest/dir/ +$ rsync --write-batch=pfx -a /source/dir/ /adest/dir/ $ rcp pfx.rsync_* remote: -$ rsh remote rsync --read_batch=pfx -a /bdest/dir/ +$ ssh remote rsync --read-batch=pfx -a /bdest/dir/ # or alternatively -$ rsh remote ./pfx.rsync_argvs /bdest/dir/ +$ ssh remote ./pfx.rsync_argvs /bdest/dir/ ) In this example, rsync is used to update /adest/dir/ with /source/dir/ @@ -1086,7 +1080,7 @@ for its transport. The way to diagnose this problem is to run your remote shell like this: verb( - rsh remotehost /bin/true > out.dat + ssh remotehost /bin/true > out.dat ) then look at out.dat. If everything is working correctly then out.dat @@ -1104,24 +1098,26 @@ show why each individual file is included or excluded. manpagesection(EXIT VALUES) startdit() -dit(bf(RERR_SYNTAX 1)) Syntax or usage error -dit(bf(RERR_PROTOCOL 2)) Protocol incompatibility -dit(bf(RERR_FILESELECT 3)) Errors selecting input/output files, dirs - -dit(bf(RERR_UNSUPPORTED 4)) Requested action not supported: an attempt +dit(bf(0)) Success +dit(bf(1)) Syntax or usage error +dit(bf(2)) Protocol incompatibility +dit(bf(3)) Errors selecting input/output files, dirs +dit(bf(4)) Requested action not supported: an attempt was made to manipulate 64-bit files on a platform that cannot support them; or an option was speciifed that is supported by the client and not by the server. - -dit(bf(RERR_SOCKETIO 10)) Error in socket IO -dit(bf(RERR_FILEIO 11)) Error in file IO -dit(bf(RERR_STREAMIO 12)) Error in rsync protocol data stream -dit(bf(RERR_MESSAGEIO 13)) Errors with program diagnostics -dit(bf(RERR_IPC 14)) Error in IPC code -dit(bf(RERR_SIGNAL 20)) Received SIGUSR1 or SIGINT -dit(bf(RERR_WAITCHILD 21)) Some error returned by waitpid() -dit(bf(RERR_MALLOC 22)) Error allocating core memory buffers -dit(bf(RERR_TIMEOUT 30)) Timeout in data send/receive +dit(bf(5)) Error starting client-server protocol +dit(bf(10)) Error in socket IO +dit(bf(11)) Error in file IO +dit(bf(12)) Error in rsync protocol data stream +dit(bf(13)) Errors with program diagnostics +dit(bf(14)) Error in IPC code +dit(bf(20)) Received SIGUSR1 or SIGINT +dit(bf(21)) Some error returned by waitpid() +dit(bf(22)) Error allocating core memory buffers +dit(bf(23)) Partial transfer due to error +dit(bf(24)) Partial transfer due to vanished source files +dit(bf(30)) Timeout in data send/receive enddit() manpagesection(ENVIRONMENT VARIABLES)