rcp: Copy files between machines
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 ‘:’
characters, or a ‘/’ before any ‘:’s).
rcp [option]… old-file new-file rcp [option]… files… directory
Use only IPv4.
Use only IPv6.
Copy all source arguments into directory.
(Server mode only.) Copying from remote host.
The option requests rcp to obtain tickets for the remote host in realm realm instead of the remote host’s realm.
Turns off all Kerberos authentication.
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 the target file are preserved
if the target itself already exists; otherwise the mode of the source
file is modified by the
umask setting on the destination host.
If any of the source files are directories,
rcp copies each
subtree rooted at that name; in this case the destination must be a
(Server mode only.) Copying to remote host.
Turns on encryption for all data passed via the
This may impact response time and CPU utilization, but provides increased
rcp doesn’t detect all cases where the target of a copy
might be a file in cases where only a directory should be legal.
rcp can be confused by any output generated by commands in a
.login, .profile, or .cshrc file on the remote
The destination user and hostname may have to be specified as
‘rhost.rname’ when the destination machine is running the 4.2BSD