HP-UX Reference (11i v1 00/12) - 1 User Commands N-Z (vol 2)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1/neqn.1
________________________________________________________________
___ ___
r
rcp(1) rcp(1)
specified, rcp preserves the sticky bit only if the target user is superuser.
If the -p option is not specified, rcp preserves the mode and owner of dest_file if it
already exists; otherwise rcp uses the mode of the source file modified by the umask
on the destination host. Modification and access times of the destination file are set to
the time when the copy was made.
-S size This option sets the size of the socket send buffer.
-R size This option sets the size of the socket receive buffer.
-r Recursively copy directory subtrees rooted at the source directory name. If any direc-
tory subtrees are to be copied, rcp recursively copies each subtree rooted at the
specified source directory name to directory dest_dir.Ifsource_dir is being copied to
an existing directory of the same name, rcp creates a new directory source_dir
within dest_dir and copies the subtree rooted at source_dir to dest_dir/source_dir.If
dest_dir does not exist, rcp first creates it and copies the subtree rooted at source_dir
to dest_dir and the output will be similar irrespective of whether a wildcard character
(source_dir/*) is used for copying or otherwise.
Constructing File and Directory Names
As indicated above, file and directory names contain one, two, or four component parts:
user_name Login name to be used for accessing directories and files on remote system.
hostname Hostname of remote system where directories and files are located.
pathname Absolute directory path name or directory path name relative to the login directory of
user user_name.
filename Actual name of source or destination file. File name expansion is allowed on source file
names.
dirname Actual name of source or destination directory subtree. File name expansion is allowed
on source directory names.
Each file or directory argument is either a remote file name of the form hostname:
path, or a local file name
(with a slash (
/) before any colon (:)). hostname can be either an official host name or an alias (see
hosts(4)). If hostname is of the form ruser
@rhost, ruser is used on the remote host instead of the current
user name. An unspecified path (that is, hostname:) refers to the remote user’s login directory. If path
does not begin with
/, it is interpreted relative to the remote user’s login directory on hostname. Shell
metacharacters in remote paths can be quoted with backslash (
\), single quotes (’’), or double quotes (""),
so that they will be interpreted remotely.
The
rcp routine does not prompt for passwords. The current local user name or any user name specified
via ruser must exist on rhost and allow remote command execution via remsh(1) and rcmd(3N).
remshd(1M) must be executable on the remote host.
Third-Party Transfers
Third-party transfers in the following form:
rcp ruser1@rhost1:path1 ruser2@rhost2:path2
are performed as:
remsh rhost1 -l ruser1 rcp path1 ruser2@rhost2:path2
Therefore, for a such a transfer to succeed, ruser2 on rhost2 must allow access by ruser1 from rhost1 (see
hosts.equiv(4)).
WARNINGS
The
rcp routine is confused by any output generated by commands in a .cshrc file on the remote host
(see csh(1)).
Copying a file onto itself, for example:
rcp path ‘hostname‘:path
may produce inconsistent results. The current HP-UX version of rcp simply copies the file over itself.
However, some implementations of
rcp, including some earlier HP-UX implementations, corrupt the file.
In addition, the same file may be referred to in multiple ways, for example, via hard links, symbolic links,
or NFS. It is not guaranteed that
rcp will correctly copy a file over itself in all cases.
HP-UX Release 11i: December 2000 − 2 − Section 1−−761
___
___