rcp - Remote file copy


rcp [ -abq ] [ -f from ] [ -s subject ] file user@site


Use rcp to send text or binary files (of any type and length) to a user on a remote system. The syntax is similar to the standard cp command which copies a file on the local system, only you specify a mail address in the user@site format as the target. Multiple users can be specified, but multiple files cannot.



By including the -a option, rcp sends an ASCII text file as one letter to the recipient. The text file appears as one message in the user’s mailbox.


Binary mode (the default). Binary mode works only between point-to-point ProLine sites. Intermediate non-ProLine sites will corrupt the file. The recipient receives an accompanying letter, generated by rcp, in his mailbox, reporting the status of the remote copy transfer. The binary portion is saved into his user directory with the same name as the original file, and all file attributes are preserved.

-f from

Allows the super user to specify the original sender.


Quiet mode.


Rcp uses a the name of the file being sent as the subject. If the -s option is given, the argument that follows becomes the subject.


The system administrator can deny a user reception of rcp files by creating a file called “rcpstop” in the user’s $/adm area. This is desirable with public accounts.

Directory files cannot be sent.


The user should exercise caution in sending binary files without knowing the path the file will take through the network. Raw binary (8-bit) files are supported only by ProLine mail systems. Should such files pass through a non-ProLine system that strips high bits and control codes, the recipient will receive a corrupted file. To ensure success in all cases, binary files should first be archived and then encoded into a text (7-bit) format before being sent with rcp. The uuencode utility provides such a feature.

See Also

par(C), path(NET), uuencode(C)