FreeBSD Manual Pages
RSH(1) OpenBSD Reference Manual RSH(1) NAME rsh - remote shell SYNOPSIS rsh [-Kdnx] [-k realm] [-l username] hostname [command] DESCRIPTION rsh executes command on hostname. 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 command to its standard error. Interrupt, quit and terminate signals are propagated to the remote command; rsh normally terminates when the remote command does. The options are as follows: -K Disable all Kerberos authentication. -d Enable socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host. -k Causes rsh to obtain tickets for the remote host in realm instead of the remote host's realm as determined by krb_realmofhost(3). -l By default, the remote username is the same as the local user- name. The -l option allows the remote name to be specified. Kerberos authentication is used, and authorization is determined as in rlogin(1). -n Redirect input from the special device /dev/null (see the BUGS section of this manual page). If no command is specified, you will be logged in on the remote host us- ing rlogin(1). If rsh is not invoked with the standard program name (``rsh''), it uses this name as its hostname argument. Shell meta-characters which are not quoted are interpreted on local ma- chine, while quoted meta-characters are interpreted on the remote ma- chine. For example, the command rsh otherhost cat remotefile >> localfile appends the remote file remotefile to the local file localfile, while rsh otherhost cat remotefile ">>" other_remotefile appends remotefile to other_remotefile. FILES /etc/hosts SEE ALSO rlogin(1), kerberos(3), krb_realmofhost(3), krb_sendauth(3), rcmd(3) HISTORY The rsh command appeared in 4.2BSD. BUGS If you are using csh(1) and put a rsh 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 rsh to /dev/null using the -n option. You cannot run an interactive command (like rogue(6) or vi(1)) using rsh; use rlogin(1) instead. Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here. rsh does not currently support encryption of the datastream when Kerberos authentication is used. OpenBSD 3.1 July 24, 1991 2
NAME | SYNOPSIS | DESCRIPTION | FILES | SEE ALSO | HISTORY | BUGS
Want to link to this manual page? Use this URL:
<https://www.freebsd.org/cgi/man.cgi?query=rsh&sektion=1&manpath=OpenBSD+3.1>