RSH(1) BSD Reference Manual RSH(1) NNAAMMEE rrsshh - remote shell SSYYNNOOPPSSIISS rrsshh [--KKddnnxx] [--kk _r_e_a_l_m] [--ll _u_s_e_r_n_a_m_e] _h_o_s_t [command] DDEESSCCRRIIPPTTIIOONN RRsshh executes _c_o_m_m_a_n_d on _h_o_s_t. RRsshh 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; rrsshh normally terminates when the remote command does. The options are as follows: --KK The --KK option turns off all Kerberos authentication. --dd The --dd option turns on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host. --kk The --kk option causes rrsshh to obtain tickets for the remote host in _r_e_a_l_m instead of the remote host's realm as determined by krb_realmofhost(3). --ll By default, the remote username is the same as the local username. The --ll option allows the remote name to be specified. Kerberos au- thentication is used, and authorization is determined as in rlogin(1). --nn The --nn option redirects input from the special device _/_d_e_v_/_n_u_l_l (see the _B_U_G_S section of this manual page). --xx The --xx option turns on DES encryption for all data exchange. This may introduce a significant delay in response time. If no _c_o_m_m_a_n_d is specified, you will be logged in on the remote host us- ing rlogin(1). Shell metacharacters which are not quoted are interpreted on local ma- chine, while quoted metacharacters are interpreted on the remote machine. For example, the command rsh otherhost cat remotefile >> localfile appends the remote file _r_e_m_o_t_e_f_i_l_e to the local file _l_o_c_a_l_f_i_l_e, while rsh otherhost cat remotefile ">>" other_remotefile 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. FFIILLEESS /etc/hosts SSEEEE AALLSSOO rlogin(1), kerberos(3), krb_sendauth(3), krb_realmofhost(3) HHIISSTTOORRYY The rrsshh command appeared in 4.2BSD. BBUUGGSS If you are using csh(1) and put a rrsshh in the background without redirect- ing its input away from the 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 rrsshh to _/_d_e_v_/_n_u_l_l using the --nn option. You cannot run an interactive command (like rogue(6) or vi(1)) using rrsshh; use rlogin(1) instead. Stop signals stop the local rrsshh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here. 4.2 Berkeley Distribution June 6, 1993 2