4.3BSD-UWisc/man/cat1/rcp.1c

RCP(1C)             UNIX Programmer's Manual              RCP(1C)



NAME
     rcp - remote file copy

SYNOPSIS
     rcp [ -p ] file1 file2
     rcp [ -p ] [ -r ] file ... directory

DESCRIPTION
     _R_c_p 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
     ``rhost:path'', or a local file name (containing no `:'
     characters, or a `/' before any `:'s).

     If the -r option is specified and any of the source files
     are directories, _r_c_p copies each subtree rooted at that
     name; in this case the destination must be a directory.

     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 modi-
     fied by the _u_m_a_s_k(2) on the destination host is used.  The
     -p option causes _r_c_p to attempt to preserve (duplicate) in
     its copies the modification times and modes of the source
     files, ignoring the _u_m_a_s_k.

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

     _R_c_p does not prompt for passwords; your current local user
     name must exist on _r_h_o_s_t and allow remote command execution
     via _r_s_h(1C).

     _R_c_p handles third party copies, where neither source nor
     target files are on the current machine.  Hostnames may also
     take the form ``rname@rhost'' to use _r_n_a_m_e rather than the
     current user name on the remote host.  The destination host-
     name may also take the form ``rhost.rname'' to support des-
     tination machines that are running 4.2BSD versions of _r_c_p.

SEE ALSO
     cp(1), ftp(1C), rsh(1C), rlogin(1C)

BUGS
     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 .login,
     .profile, or .cshrc file on the remote host.







Printed 12/27/86          May 12, 1986                          1