Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

cp(1)

ftp(1C)

rsh(1C)

rlogin(1C)

RCP(1C)                              BSD                               RCP(1C)



NAME
     rcp - remote file copy

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

DESCRIPTION
     The rcp command copies files between machines. Each file or directory
     argument is either a remote file name of the form rhost:path, or a local
     filename containing no colon characters (:) or a slash mark (/) before
     any colons (:).

     By default, rcp preserves the mode and owner of file2 if it already
     existed; otherwise the mode of the source file modified by the umask(2)
     on the destination host is used.

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

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

     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 rname rather than the current user name on the remote host.  The
     destination hostname may also take the form host.rname to support
     destination machines that are running 4.2BSD versions of rcp.

OPTIONS
     -r        If any of the source files are directories, copy each subtree
               rooted at that name; in this case the destination must be a
               directory.

     -p        Attempt to preserve (duplicate) in copies the modification
               times and modes of the source files, ignoring the umask.

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.

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

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026