REMSH(1) Series 300 Only REMSH(1)
NAME
remsh - remote shell
SYNOPSIS
remsh host [ -l username ] [ -n ] command
host [ -l username ] [ -n ] command
HP-UX COMPATIBILITY
Level: HP-UX/NON-STANDARD
Origin: UCB
Remarks: Remsh is the same service as rsh on 4.2BSD. The
name was changed due to a conflict with the
existing system V command rsh (restricted shell).
Implemented on the Series 300 only.
DESCRIPTION
Remsh connects to the specified host, and executes the
specified command. The hostname can be either the official
name or an alias, as listed in /etc/hosts; see hosts(5).
Remsh copies its standard input (stdin) to the remote
command, the standard output of the remote command to its
standard output (stdout), and the standard error of the
remote command to its standard error (stderr). Interrupt,
quit and terminate signals are propagated to the remote
command. Remsh normally terminates when the remote command
does. Remsh uses the following path when executing the
specified command:
/bin:/usr/bin:/usr/contrib/bin:/usr/local/bin
You cannot run an interactive command (like more(1), or
vi(1)) with remsh. For those commands, you should use
rlogin(1).
The remote account name used is the same as your local
account name, unless you specify a different remote name
with the -l option. This remote account name must be
equivalent to the originating account; no provision is made
for specifying a password with a command. For more details
about ``equivalent'' hosts and how to specify them, see
hosts.equiv(5). The files inspected by remshd(1M) on the
remote host are /etc/hosts.equiv and $HOME/.rhosts.
If you omit command, then instead of executing a single
command, you will be logged in on the remote host using
rlogin(1), and whatever rlogin options you have typed in the
command line will be transmitted to rlogin. If command is
specified then options specific to rlogin are ignored by
remsh.
Hewlett-Packard - 1 - (printed 7/16/86)
REMSH(1) Series 300 Only REMSH(1)
The -n option redirects the input of remsh from /dev/null.
Shell metacharacters which are not quoted are interpreted on
the local host, while quoted metacharacters are interpreted
on the remote host. Thus the command
remsh otherhost cat remotefile >> localfile
appends the remote file remotefile to the local file
localfile, while
remsh otherhost cat remotefile ">>" otherremotefile
appends remotefile to the remote file otherremotefile.
Official host names and their aliases are given in the file
/etc/hosts; see hosts(5). The host names for remote hosts
can also be commands (linked to remsh) in the directory
/usr/hosts; if you put this directory in your search path
then the remsh can be omitted. So, for example, if
``remotehost'' is the name of a remote host and
/usr/hosts/remotehost is linked to remsh, and if /usr/hosts
is in your search path then the command
remotehost command
executes ``command'' on ``remotehost''.
DIAGNOSTICS
Besides the errors listed below, errors can also be
generated by the libraries rcmd and rresvport which are used
by remsh (see rcmd(3X)). Those errors are preceded by the
name of the library that generated them. The diagnostic
messages for remsh are the following:
rlogin: ...
Error in executing rlogin (rlogin is called when the
user does not specify any commands to be executed).
This is followed by the error message specifying why
the execution failed.
shell/tcp: Unknown service
The ``shell'' service specification is not present in
the /etc/services file.
Can't establish stderr
Remsh cannot establish secondary socket connection for
stderr.
<system call>: ...
Error in executing system call. Appended to this error
is a message specifying the cause of the failure.
Hewlett-Packard - 2 - (printed 7/16/86)
REMSH(1) Series 300 Only REMSH(1)
There is no entry for you (user ID <uid>) in /etc/passwd
Check with the system administrator to see if your
entry in the password file has been deleted by mistake.
FILES
/etc/hosts host name data base
/usr/hosts/* for version of the command invoked only with
hostname
SEE ALSO
rlogin(1), remshd(1M), hosts.equiv(5), hosts(5).
WARNINGS
For security purposes, the /etc/hosts.equiv and .rhosts
files should exist, even if empty, and should be readable
and writable only by the owner. Note also that all
information, including any passwords asked for, is passed
unencrypted between the two hosts.
If remsh is run with an interactive command it will hang.
Hewlett-Packard - 3 - (printed 7/16/86)