Return to rcp.1c CVS log

Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man1

Power 6/32 Unix version 1.21

.TH RCP 1C "17 March 1982"
.UC 4
.SH NAME
rcp \- remote file copy
.SH SYNOPSIS
.B rcp
file1 file2
.br
.B rcp
[
.B \-r
] file ... directory
.SH DESCRIPTION
.I 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
is specified and any of the source files are directories,
.I rcp
copies each subtree rooted at that name; in this case
the destination must be a directory.
.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
.I Rcp
does not prompt for passwords; your current local user name
must exist on
.I rhost
and allow remote command execution via
.IR rsh (1C).
.PP
.I Rcp
handles third party copies, where neither source nor target files
are on the current machine.
Hostnames may also take the form ``rhost.rname'' to use
.I rname
rather than the current user name on the remote host.
For example, for the current user is 
.I user1 
and his local host is 
.I host1,
then the following command
.RS

rcp host2.userB:filea host3.userC:fileb

.RE
will copy
.I filea
in the home directory of 
.I userB@host2
to
.I fileb
in the home directory of
.I userC@host3
provided that the entry "host1 userA" is in
.I .rhosts
of 
.I userB@host2,
and "host2 userB" in
.I .rhosts
of 
.I userC@host3.
.SH SEE ALSO
ftp(1C), rsh(1C), rlogin(1C)
.SH FILES
/etc/hosts.equiv
.br
".rhosts" in user's home directory
.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.
.PP
Users might be confused by any output generated by commands in a
\&.login, \&.profile, or \&.cshrc file on the remote host. Particularly,
commands setting terminal attributes in the shell startup files 
of remote accounts might fail
since the remote shell is not associated with terminals.
.PP
See also
.I .rlogin
for the bugs on parsing the equivalence list in
.I /etc/.rhosts
or
.I .rhosts
in the user home directory.
.PP

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.