rcp(1c) [ultrix man page]
rcp(1c) rcp(1c) Name rcp - remote file copy Syntax rcp [ -p ] file1 file2 rcp [-r] [-p] file... directory Description The command copies files between machines. Each file or directory argument is either a remote file name of the form rhost:path, or a local file name. Local file names do not contain colons (:) or backslashes () before colons. Note that the command refuses to copy a file onto itself. If path is not a full path name, it is interpreted relative to your login directory on rhost. To ensure that the metacharacters are inter- preted remotely, a remote host's path can be quoted by either using a backslash () before a single character, or enclosing character strings in double (") or single (') quotes. The command does not prompt for passwords; your current local user name must exist on rhost and allow remote command execution via The command 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 rname rather than the current user name on the remote host. The following example shows how to copy the file foo from user1@mach1 to user2@mach2: $ rcp user1@mach1:foo user2@mach2:foo Note that the file .rhosts on mach2 in user2's account must include an entry for mach1 user1. Also note that it may be necessary for the person implementing the command to be listed in the .rhosts file for mach1 user1. By default, the mode and owner of file2 are preserved if file2 already exists. Otherwise, the mode of the source file modified by on the destination host is used. Options -p Preserves the modification times and modes of the source files in its copies, ignoring the -r Copies files in all subdirectories recursively, if the file to be copied is a directory. In this case the destination must be a directory. Restrictions The command is confused by output generated by commands in a .cshrc file on the remote host. In particular, `where are you?' and `stty: Can't assign requested address' are messages which can result if output is generated by the startup file. See Also ftp(1c), rlogin(1c), rsh(1c) rcp(1c)
Check Out this Related Man Page
RCP(1) BSD General Commands Manual RCP(1) NAME
rcp -- remote file copy SYNOPSIS
rcp [-46p] file1 file2 rcp [-46pr] file ... directory DESCRIPTION
rcp copies files between machines. Each file or directory argument is either a remote file name of the form ``rname@rhost:path'', or a local file name (containing no ':' (colon) characters, or a '/' (slash) before any ':' (colon) characters). The rhost can be an IPv4 or an IPv6 address string. Since IPv6 addresses already contain ':' (colon) characters, an IPv6 address string must be enclosed between '[' (left square bracket) and ']' (right square bracket) characters. Otherwise, the first occurrence of a ':' (colon) character would be interpreted as the separator between the rhost and the path. For example, [2001:DB8::800:200C:417A]:tmp/file Options: -4 Use IPv4 addresses only. -6 Use IPv6 addresses only. -p The -p option causes rcp to attempt to preserve (duplicate) in its copies the modification times and modes of the source files, ignor- ing the umask. By default, the mode and owner of file2 are preserved if it already existed; otherwise the mode of the source file mod- ified by the umask(2) on the destination host is used. -r If any of the source files are directories, rcp copies each subtree rooted at that name; in this case the destination must be a direc- tory. If path is not a full path name, it is interpreted relative to the login directory of the specified user ruser on rhost, or your current user name if no other remote user name is specified. A path on a remote host may be quoted (using , ", or ') so that the metacharacters are interpreted remotely. rcp does not prompt for passwords; it performs remote execution via rsh(1), and requires the same authorization. rcp handles third party copies, where neither source nor target files are on the current machine. SEE ALSO
cp(1), ftp(1), rcmd(1), rlogin(1), rsh(1), rcmd(3), hosts.equiv(5), rhosts(5), environ(7) HISTORY
The rcp utility appeared in 4.2BSD. The version of rcp described here has been reimplemented with Kerberos in 4.3BSD-Reno. 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. The destination user and hostname may have to be specified as ``rhost.rname'' when the destination machine is running the 4.2BSD version of rcp. BSD
March 8, 2005 BSD