Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

Chapter 10 213
Technical Articles
The REMSH Client Functionality
run remsh.net.sys;info="remotehost -l remoteuser [-n]
remotecommand"
jhereg(PUB): run remsh.net.sys;info="taltos -l cawti -n pwd"
/u2/home/cawti
jhereg(PUB):
Posix Examples
From the Posix Shell prompt, type:
/SYS/NET/REMSH remotehost -l remoteuser [-n] remotecommand
shell/iX> /SYS/NET/REMSH taltos -l cawti -n pwd
/u2/home/cawti
shell/iX>
Since you are running under the Posix shell, there are a number of shell
features that you can take advantage of.
Shell metacharacters that are not quoted are interpreted on the local
host; quoted metacharacters are interpreted on the remote host. The
following command line appends the remotefile to the local file localfile:
SYS/NET/REMSH taltos -l cawti cat remotefile >> localfile
The following command line appends remotefile to the otherremotefile:
/SYS/NET/REMSH taltos -l cawti cat remotefile ">>" otherremotefile
The following command line runs REMSH in the background on the local
system, and the output of the remote command comes to your terminal
asynchronously:
/SYS/NET/REMSH otherhost -l remoteuser -n remotecommand
The following command line causes REMSH to return immediately
without waiting for the remote command to complete:
/SYS/NET/REMSH otherhost -l remoteuser -n
"remotecommand 1>&- 2>&- &"
In REMSH, if the first parameter in its argument vector is not REMSH,
it will use the value as a host name. You may symbolically link the host
name to the REMSH program. A typical BSD UNIX implementation
will have these links under the /usr/hosts directory.
If you have made a symbolic link to the REMSH program that is the
host name (that is in our examples, ln -s /SYS/NET/REMSH
taltos), you could generate the same result as the first example with
the following:
shell/iX>taltos -l cawti -n pwd
/u2/home/cawti
shell/iX>
Troubleshooting REMSH
These are the REMSH messages with an explanation of the meaning
and suggested action, if any.