.\" from: rcp.1,v 4.1 89/01/23 11:39:00 jtkohl Exp $ .\" $Id: rcp.1,v 1.2 1994/07/19 19:28:00 g89r4222 Exp $ .\" .\" Copyright (c) 1983 The Regents of the University of California. .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms are permitted .\" provided that the above copyright notice and this paragraph are .\" duplicated in all such forms and that any documentation, .\" advertising materials, and other materials related to such .\" distribution and use acknowledge that the software was developed .\" by the University of California, Berkeley. The name of the .\" University may not be used to endorse or promote products derived .\" from this software without specific prior written permission. .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED .\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. .\" .\" @(#)rcp.1 6.6 (Berkeley) 9/20/88 .\" .TH RCP 1 "Kerberos Version 4.0" "MIT Project Athena" .UC 5 .SH NAME rcp \- remote file copy .SH SYNOPSIS .B rcp [ .B \-p ] [ .B \-x ] [ .B \-k realm ] file1 file2 .br .B rcp [ .B \-p ] [ .B \-x ] [ .B \-k realm ] [ .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 option 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 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 .IR umask (2) on the destination host is used. The .B \-p option causes .I rcp to attempt to preserve (duplicate) in its copies the modification times and modes of the source files, ignoring the .IR 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 .I Rcp does not prompt for passwords; it uses Kerberos authentication when connecting to .IR rhost . Authorization is as described in .IR rlogin (1). .PP The .B \-x option selects encryption of all information transferring between hosts. The .B \-k .I realm option causes .I rcp to obtain tickets for the remote host in .I realm instead of the remote host's realm as determined by .IR krb_realmofhost (3). .PP .I 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. .SH SEE ALSO cp(1), ftp(1), rsh(1), rlogin(1), kerberos(3), krb_getrealm(3), rcp(1) [UCB version] .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 Is confused by any output generated by commands in a \&.login, \&.profile, or \&.cshrc file on the remote host. .PP The destination user and hostname may have to be specified as ``rhost.rname'' when the destination machine is running the 4.2BSD version of \fIrcp\fP. .PP Kerberos is only used for the first connection of a third-party copy; the second connection uses the standard Berkeley rcp protocol.