2.11BSD#431 - /usr/man/cat1/rsh.0

RSH(1C)             UNIX Programmer's Manual		  RSH(1C)


NAME
     rsh - remote shell

SYNOPSIS
     rsh host [ -l username ] [ -n ] command
     host [ -l username ] [ -n ] command

DESCRIPTION
     Rsh connects to the specified host, and executes the speci-
     fied command.  Rsh copies its standard input to the remote
     command, the standard output of the remote command to its
     standard output, and the standard error of the remote com-
     mand to its standard error.  Interrupt, quit and terminate
     signals are propagated to the remote command; rsh normally
     terminates when the remote command does.

     The remote username used is the same as your local username,
     unless you specify a different remote name with the -l
     option.  This remote name must be equivalent (in the sense
     of rlogin(1C)) to the originating account; no provision is
     made for specifying a password with a command.

     If you omit command, then instead of executing a single com-
     mand, you will be logged in on the remote host using
     rlogin(1C).

     Shell metacharacters which are not quoted are interpreted on
     local machine, while quoted metacharacters are interpreted
     on the remote machine.  Thus the command

	rsh otherhost cat remotefile >> localfile

     appends the remote file remotefile to the localfile local-
     file, while

	rsh otherhost cat remotefile ">>" otherremotefile

     appends remotefile to otherremotefile.

     Host names are given in the file /etc/hosts.  Each host has
     one standard name (the first name given in the file), which
     is rather long and unambiguous, and optionally one or more
     nicknames.  The host names for local machines are also com-
     mands in the directory /usr/hosts; if you put this directory
     in your search path then the rsh can be omitted.

FILES
     /etc/hosts
     /usr/hosts/*

SEE ALSO
     rlogin(1C)


Printed 11/26/99	 April 29, 1985                         1


RSH(1C)             UNIX Programmer's Manual		  RSH(1C)


BUGS
     If you are using csh(1) and put a rsh(1C) in the background
     without redirecting its input away from the terminal, it
     will block even if no reads are posted by the remote com-
     mand.  If no input is desired you should redirect the input
     of rsh to /dev/null using the -n option.

     You cannot run an interactive command (like rogue(6) or
     vi(1)); use rlogin(1C).

     Stop signals stop the local rsh process only; this is argu-
     ably wrong, but currently hard to fix for reasons too com-
     plicated to explain here.


Printed 11/26/99	 April 29, 1985                         2