[1mSYNOPSIS[0m
[1mrcp [22m[[1m-p[22m] [[1m-x[22m] [[1m-k [4m[22mrealm[24m ] [[1m-c [4m[22mccachefile[24m] [[1m-C [4m[22mconfigfile[24m] [[1m-D [4m[22mport[24m]
[[1m-N[22m] [[1m-PN | -PO[22m] [4mfile1[24m [4mfile2[0m
[1mrcp [22m[[1m-p] [-x] [-k [4m[22mrealm[24m[1m] [-r] [-D [4m[22mport[24m[1m] [-N] [-PN | -PO] [4m[22mfile[24m [4m...[0m
[4mdirectory[0m
[1mrcp [22m[[1m-f | -t[22m] [4m...[0m
[1mDESCRIPTION[0m
[1mRcp [22mcopies files between machines. Each [4mfile[24m or [4mdirectory[24m argument is
either a remote file name of the form ``rhost:path'', or a local file
name (containing no `:' characters, or a `/' before any `:'s).
By default, the mode and owner of [4mfile2[24m are preserved if it already
existed; otherwise the mode of the source file modified by the [4mumask[24m(2)
on the destination host is used.
If [4mpath[24m is not a full path name, it is interpreted relative to your
login directory on [4mrhost[24m. A [4mpath[24m on a remote host may be quoted (using
\, ", or ') so that the metacharacters are interpreted remotely.
[1mRcp [22mdoes not prompt for passwords; it uses Kerberos authentication when
connecting to [4mrhost[24m. Each user may have a private authorization list
in a file .k5login in his login directory. Each line in this file
should contain a Kerberos principal name of the form [4mprinci-[0m
[4mpal/instance@realm[24m. If there is a ~/.k5login file, then access is
granted to the account if and only if the originater user is authenti-
cated to one of the principals named in the ~/.k5login file. Other-
wise, the originating user will be granted access to the account if and
only if the authenticated principal name of the user can be mapped to
the local account name using the aname -> lname mapping rules (see
[4mkrb5_anadd[24m(8) for more details).
[1mOPTIONS[0m
[1m-p [22mattempt to preserve (duplicate) the modification times and modes
of the source files in the copies, ignoring the [4mumask[24m.
[1m-x [22mencrypt all information transferring between hosts.
[1m-k [4m[22mrealm[0m
obtain tickets for the remote host in [4mrealm[24m instead of the
remote host's realm as determined by [4mkrb_realmofhost[24m(3).
[1m-c [4m[22mccachefile[0m
change the default credentials cache file to [4mccachefile[0m
[1m-C [4m[22mconfigfile[0m
change the default configuation file to [4mconfigfile[0m
[1m-r [22mif any of the source files are directories, copy each subtree
rooted at that name; in this case the destination must be a
[1m-N [22muse a network connection, even when copying files on the local
machine (used for testing purposes).
[1m-f -t [22mThese options are for internal use only. They tell the
remotely-running rcp process (started via the Kerberos remote
shell daemon) which direction files are being sent. These
options should not be used by the user. In particular, [1m-f [22mdoes
[1mnot [22mmean that the user's Kerberos ticket should be forwarded!
[1mRcp [22mhandles third party copies, where neither source nor target files
are on the current machine. Hostnames may also take the form
``rname@rhost'' to use [4mrname[24m rather than the current user name on the
remote host.
[1mFILES[0m
~/.k5login (on remote host) - file containing Kerberos principals that
are allowed access.
[1mSEE ALSO[0m
cp(1), ftp(1), rsh(1), rlogin(1), kerberos(3), krb_getrealm(3),
kshd(8), rcp(1) [UCB version]
[1mBUGS[0m
[1mRcp [22mdoesn't detect all cases where the target of a copy might be a file
in cases where only a directory should be legal.
[1mRcp [22mis confused by any output generated by commands in a .login, .pro-
file, or .cshrc file on the remote host.
Kerberos is only used for the first connection of a third-party copy;
the second connection uses the standard Berkeley rcp protocol.
RCP(1)
Man(1) output converted with
man2html