|-4||Use IPv4 addresses only.|
|-6||Use IPv6 addresses only.|
|-d||Turn on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.|
|Allow the remote username to be specified. By default, the remote username is the same as the local username. Authorization is determined as in rlogin(1).|
|-n||Redirect input from the special device /dev/null (see the BUGS section of this manual page).|
|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.
rlogin(1), setsockopt(2), rcmd(3), ruserok(3), hosts(5), hosts.equiv(5), rlogind(8), rshd(8)
The rsh command appeared in BSD 4.2 .
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.
Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here.