.\" Copyright (c) 1983 Regents of the University of California.
.\" All rights reserved.  The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\"
.\"	@(#)rcp.1c	6.4 (Berkeley) 5/12/86
.\"
.TH RCP 1 "May 12, 1986"
.UC 5
.SH NAME
rcp \- remote file copy
.SH SYNOPSIS
.B rcp
.RB [ \-p ]
.I file1 file2
.br
.B rcp
.RB [ \-pr ]
.I file
\&...
.I directory
.SH DESCRIPTION
.B Rcp
copies files between machines.  Each
.I file
or
.I directory
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).
.PP
If the
.B \-r
option
is specified and any of the source files are directories,
.B rcp
copies each subtree rooted at that name; in this case
the destination must be a directory.
.PP
By default, the mode and owner of
.I file2
are preserved if it already existed; otherwise the mode of the source file
modified by the
.BR umask (2)
on the destination host is used.
The
.B \-p
option causes
.B rcp
to attempt to preserve (duplicate) in its copies the modification
times and modes of the source files, ignoring the
.BR umask .
.PP
If
.I path
is not a full path name, it is interpreted relative to
your login directory on 
.IR rhost .
A 
.I path
on a remote host may be quoted (using \e, ", or \(aa)
so that the metacharacters are interpreted remotely.
.PP
.B Rcp
does not prompt for passwords; your current local user name
must exist on
.I rhost
and allow remote command execution via
.BR rsh (1).
.PP
.B Rcp
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
.I rname
rather than the current user name on the remote host.
The destination hostname may also take the form ``rhost.rname'' to
support destination machines that are running 4.2BSD
versions of
.BR rcp .
.SH SEE ALSO
.BR cp (1),
.BR ftp (1),
.BR rsh (1),
.BR rlogin (1).
.SH 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.
.br
Is confused by any output generated by commands in a
\&.profile, or \&.*shrc file on the remote host.