


      RRRRSSSSHHHH((((1111))))                      ((((bbbbssssdddd 4444....2222))))                      RRRRSSSSHHHH((((1111))))



      NNNNAAAAMMMMEEEE
           rsh - remote shell

      SSSSYYYYNNNNTTTTAAAAXXXX
           rrrrsssshhhh host [ ----llll username ] [ ----nnnn ] command

      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
           _R_s_h connects to the specified _h_o_s_t, and executes the
           specified _c_o_m_m_a_n_d.  _R_s_h 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
           command to its standard error.  Interrupt, quit and
           terminate signals are propagated to the remote command; _r_s_h
           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 ----llll
           option.  This remote name must be equivalent (in the sense
           of _r_l_o_g_i_n(1)) to the originating account; no provision is
           made for specifying a password with a command.

           If you omit _c_o_m_m_a_n_d, then, instead of executing a single
           command, you will be logged in on the remote host using
           _r_l_o_g_i_n(1).

           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 _r_e_m_o_t_e_f_i_l_e to the localfile
           _l_o_c_a_l_f_i_l_e, while

              rsh otherhost cat remotefile ">>" otherremotefile

           appends _r_e_m_o_t_e_f_i_l_e to _o_t_h_e_r_r_e_m_o_t_e_f_i_l_e.

           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.

      FFFFIIIILLLLEEEESSSS
           /etc/hosts

      SSSSEEEEEEEE AAAALLLLSSSSOOOO
           rlogin(1)

      BBBBUUUUGGGGSSSS
           If you are using _c_s_h(1) and you put a _r_s_h(1) in the
           background without redirecting its input away from the



      Page 1                                                   (9010-E)






      RRRRSSSSHHHH((((1111))))                      ((((bbbbssssdddd 4444....2222))))                      RRRRSSSSHHHH((((1111))))



           terminal, it will block even if no reads are posted by the
           remote command.  If no input is desired, you should redirect
           the input of _r_s_h to /dev/null using the ----nnnn option.

           You cannot run an interactive command (like _v_i(1)).
           Instead, use _r_l_o_g_i_n(1).

           Stop signals terminate the local _r_s_h process only.  This is
           arguably wrong, but currently hard to fix for reasons too
           complicated to explain here.

           Remote commands that treat standard out and standard in do
           not work as usual because standard out is not a terminal for
           the remote shell.  For instance, llllllll ----CCCC must be used to force
           the long listing into a columns.








































      Page 2                                                   (9010-E)



