rcp copies files between machines. Each
file or
directory argument is either a remote file name of the form “rname@rhost:path”, or a local file name (containing no ‘:' (colon) characters, or a ‘/' (slash) before any ‘:' (colon) characters).
The
rhost can be an IPv4 or an IPv6 address string. Since IPv6 addresses already contain ‘:' (colon) characters, an IPv6 address string must be enclosed between ‘[' (left square bracket) and ‘]' (right square bracket) characters. Otherwise, the first occurrence of a ‘:' (colon) character would be interpreted as the separator between the
rhost and the
path. For example,
[2001:DB8::800:200C:417A]:tmp/file
Options:
-4
Use IPv4 addresses only.
-6
Use IPv6 addresses only.
-p
The
-p option causes
rcp to attempt to preserve (duplicate) in its copies the modification times and modes of the source files, ignoring the
umask. By default, the mode and owner of
file2 are preserved if it already existed; otherwise the mode of the source file modified by the
umask(2) on the destination host is used.
-r
If any of the source files are directories, rcp copies each subtree rooted at that name; in this case the destination must be a directory.
If
path is not a full path name, it is interpreted relative to the login directory of the specified user
ruser on
rhost, or your current user name if no other remote user name is specified. A
path on a remote host may be quoted (using \, ", or ́) so that the metacharacters are interpreted remotely.
rcp does not prompt for passwords; it performs remote execution via
rsh(1), and requires the same authorization.
rcp handles third party copies, where neither source nor target files are on the current machine.