4.3BSD-Reno/share/man/cat1/rcp.0

RCP(1)			    UNIX Reference Manual			RCP(1)

NNAAMMEE
     rrccpp - remote file copy

SSYYNNOOPPSSIISS
     rrccpp [--pp] [--kk _r_e_a_l_m] _f_i_l_e_1 _f_i_l_e_2
     rrccpp [--pp] [--rr] [--kk _r_e_a_l_m] _f_i_l_e ...	_d_i_r_e_c_t_o_r_y

DDEESSCCRRIIPPTTIIOONN
     RRccpp copies files between machines.  Each _f_i_l_e or _d_i_r_e_c_t_o_r_y 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).

     --rr        If any of the source files are directories, rrccpp copies each
	       subtree rooted at that name; in this case the destination must
	       be a directory.

     --pp        The --pp option causes rrccpp to attempt to preserve (duplicate) in
	       its copies the modification times and modes of the source
	       files, ignoring the _u_m_a_s_k.  By default, the mode and owner of
	       _f_i_l_e_2 are preserved if it already existed; otherwise the mode
	       of the source file modified by the umask(2) on the destination
	       host is used.

     --kk        The --kk option requests rrccpp to obtain tickets for the remote
	       host in realm _r_e_a_l_m instead of the remote host's realm as
	       determined by krb_realmofhost(3).

     If _p_a_t_h is not a full path name, it is interpreted relative to the login
     directory of the specified user _r_u_s_e_r on _r_h_o_s_t, or your current user name
     if no other remote user name is specified.  A _p_a_t_h on a remote host may
     be quoted (using \, ", or ') so that the metacharacters are interpreted
     remotely.

     RRccpp does not prompt for passwords; it performs remote execution via
     rsh(1), and requires the same authorization.

     RRccpp handles third party copies, where neither source nor target files are
     on the current machine.

SSEEEE AALLSSOO
     cp(1), ftp(1), rsh(1), rlogin(1)

HHIISSTTOORRYY
     RRccpp appeared in 4.2 BSD.  The version of rcp described here has been
     reimplemented with Kerberos in 4.3+Reno BSD.

BBUUGGSS
     Doesn't detect all cases where the target of a copy might be a file in
     cases where only a directory should be legal.

     Is confused by any output generated by commands in a ._l_o_g_i_n, ._p_r_o_f_i_l_e, or
     ._c_s_h_r_c file on the remote host.

     The destination user and hostname may have to be specified as
     ``rhost.rname'' when the destination machine is running the 4.2BSD ver-
     sion of rrccpp.