has been deprecated in favor of
is discouraged due to the inherent insecurity of host-based authentication.
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
normally terminates when the remote command does.
The options are as follows:
Enable socket debugging (using
sockets used for communication with the remote host.
By default, the remote username is the same as the local username.
option allows the remote name to be specified.
Redirect input from the special device
section of this manual page).
is specified, you will be logged in on the remote host using
is not invoked with the standard program name
it uses this name as its
Shell meta-characters which are not quoted are interpreted on local machine,
while quoted meta-characters are interpreted on the remote machine.
For example, the command
$ rsh otherhost cat remotefile >> localfile
appends the remote file
to the local file
$ rsh otherhost cat remotefile \&">>\&" other_remotefile
If you are using
and put a
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
Stop signals stop the local
process only; this is arguably wrong, but currently hard to fix for reasons
too complicated to explain here.