rsh -- remote shell
rsh [-46Kdnx] [-t timeout] [-k realm] [-l username] host [command]
The rsh utility executes command on host.
The rsh utility 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:
-4 Use IPv4 addresses only.
-6 Use IPv6 addresses only.
-K Turn off all Kerberos authentication.
-d Turn on socket debugging (using setsockopt(2)) on the TCP sockets
used for communication with the remote host.
-k realm
Cause rsh to obtain tickets for the remote host in realm instead of
the remote host's realm as determined by krb_realmofhost(3).
-l username
Allow the remote username to be specified. By default, the remote
username is the same as the local username. 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).
-x Turn on DES encryption for all data exchange. This may introduce a
significant delay in response time.
-t timeout
Allow a timeout to be specified (in seconds). If no data is sent
or received in this time, rsh will exit.
If no command is specified, you will be logged in on the remote host
using rlogin(1).
Shell metacharacters which are not quoted are interpreted on local
machine, while quoted metacharacters are interpreted on the remote
machine. 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.
/etc/hosts
/etc/auth.conf
rlogin(1), setsockopt(2), kerberos(3), krb_realmofhost(3),
krb_sendauth(3), rcmd(3), ruserok(3), auth.conf(5), hosts(5),
hosts.equiv(5), rlogind(8), rshd(8)
The rsh command appeared in 4.2BSD.
If you are using csh(1) and put a rsh in the background without redirecting
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.
FreeBSD 5.2.1 June 6, 1993 FreeBSD 5.2.1 [ Back ] |
