Info Node: (inetutils.info)rcp invocation

CFHT HOME inetutils.info: rcp invocation


up: Top next: rexec invocation prev: rlogin invocation Back to Software Index

14 'rcp': Copy files between machines
*************************************

'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 ':' characters, or a '/' before any ':'s).

Synopsis:

     rcp [OPTION]... OLD-FILE NEW-FILE
     rcp [OPTION]... FILES... DIRECTORY

14.1 Command line options
=========================

'-4'
'--ipv4'
     Use only IPv4.

'-6'
'--ipv6'
     Use only IPv6.

'-d DIRECTORY'
'--target-directory=DIRECTORY'
     Copy all source arguments into DIRECTORY.

'-f'
'--from'
     (Server mode only.)  Copying from remote host.

'-k REALM'
'--realm=REALM'
     The option requests rcp to obtain tickets for the remote host in
     realm REALM instead of the remote host's realm.

'-K'
'--kerberos'
     Turns off all Kerberos authentication.

'-p'
'--preserve'
     Causes 'rcp' to attempt to preserve (duplicate) in its copies the
     modification times and modes of the source files, ignoring the
     umask.  By default, the mode and owner of the target file are
     preserved if the target itself already exists; otherwise the mode
     of the source file is modified by the 'umask' setting on the
     destination host.

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

'-t'
'--to'
     (Server mode only.)  Copying to remote host.

'-x'
'--encrypt'
     Turns on encryption for all data passed via the 'rcp' session.
     This may impact response time and CPU utilization, but provides
     increased security.

   'rcp' doesn't detect all cases where the target of a copy might be a
file in cases where only a directory should be legal.

   'rcp' can be 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'.


automatically generated by info2www version 1.2