Copyright (c) 1983, 1990 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following ...
NAMErsh - remote shell
rsh [-Kdnx ] [-k realm ] [-l username ] host [command]
DESCRIPTIONRsh executes command on host
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:
- The -K option turns off all Kerberos authentication.
- The -d option turns on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.
- By default, the remote username is the same as the local username. The -l option allows the remote name to be specified. Kerberos authentication is used, and authorization is determined as in rlogin(1).
- The -n option redirects input from the special device /dev/null (see the Sx BUGS section of this manual page).
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
SEE ALSOrlogin(1), kerberos(3), krb_sendauth3, krb_realmofhost3
HISTORYThe rsh command appeared in BSD 4.2
BUGSIf 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.