DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 

rcp.mn(C)


rcp.mn -- copy files between systems in a Micnet network

Syntax

rcp.mn [ options ] [ srcmachine: ] srcfile [ destmachine: ] destfile

Description

rcp.mn copies files between systems in a Micnet network. The command copies the srcmachine:srcfile to destmachine:destfile, where srcmachine: and destmachine: are optional names of systems in the network, and srcfile and destfile are pathnames of files. If a machine name is not given, the name of the current system is assumed. If ``-'' is given in place of srcfile, rcp.mn uses the standard input as the source. Directories named on the destination machine must have write permission, and directories and files named on a remote source machine must have read permission.

The available options are:


-m
Mails and reports completion of the command, whether there is an error or not.

-u [machine:]user
Any mail goes to the named user on machine. The default machine is the machine on which the rcp.mn command is completed or on which an error was detected. If an alias for user exists in the system alias files on that machine, the mail will be redirected to the appropriate mailbox(es). Since system alias files are usually identical throughout the network, any specified machine will most likely be overridden by the aliasing mechanism. To prevent aliasing, user must be escaped with at least two ``\'' characters (at least four if given as a shell command).
rcp.mn is useful for transferring small numbers of files across the network. The network consists of daemons that periodically awaken and send files from one system to another. The network must be installed using netutil(ADM) before rcp.mn can be used.

Also, to enable transfer of files from a remote system, either:

This line should be in /etc/default/micnet on the systems in the network:

   rcp=/usr/bin/rcp.mn
Or, these lines should be in that file:
   executeall
   execpath=PATH=path
where path must contain /usr/bin.

Diagnostics

If an error occurs, mail is sent to the user.

Examples

rcp.mn -m machine1:/etc/mnttab /tmp/vtape

Limitations

Full pathnames must be specified for remote files.

rcp.mn handles binary data files transparently: no extra options or protocols are needed to handle them. Wildcards are not expanded on the remote machine.

See also

mail(C), netutil(ADM), rcp(TC), remote(C)

Standards conformance

rcp.mn is not part of any currently supported standard; it is an extension of AT&T System V provided by The Santa Cruz Operation, Inc.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005