[1mSYNOPSIS[0m
[1mrsh [4m[22mhost[24m [[1m-l [4m[22musername[24m] [[1m-n[22m] [[1m-d[22m] [[1m-k [4m[22mrealm[24m] [[1m-f [22m| [1m-F[22m] [[1m-x[22m] [[1m-PN | -PO[22m]
[4mcommand[0m
[1mDESCRIPTION[0m
[1mRsh [22mconnects to the specified [4mhost,[24m and executes the specified [4mcommand[24m.
[1mRsh [22mcopies its standard input to the remote command, the standard out-
put of the remote command to its standard output, and the standard
error of the remote command to its standard error. This implementation
of [1mrsh [22mwill accept any port for the standard error stream. Interrupt,
quit and terminate signals are propagated to the remote command; [4mrsh[0m
normally terminates when the remote command does.
Each user may have a private authorization list in a file .k5login in
his login directory. Each line in this file should contain a Kerberos
principal name of the form [4mprincipal/instance@realm[24m. If there is a
~/.k5login file, then access is granted to the account if and only if
the originater user is authenticated to one of the princiapls named in
the ~/.k5login file. Otherwise, the originating user will be granted
access to the account if and only if the authenticated principal name
of the user can be mapped to the local account name using the aname ->
lname mapping rules (see [4mkrb5_anadd[24m(8) for more details).
[1mOPTIONS[0m
[1m-l [4m[22musername[0m
sets the remote username to [4musername[24m. Otherwise, the remote
username will be the same as the local username.
[1m-x [22mcauses the network session traffic to be encrypted. This
applies only to the input and output streams, and not the com-
mand line.
[1m-f [22mcause nonforwardable Kerberos credentials to be forwarded to the
remote machine for use by the specified [4mcommand[24m. They will be
removed when [4mcommand[24m finishes. This option is mutually exclu-
sive with the [1m-F [22moption.
[1m-F [22mcause [4mforwardable[24m Kerberos credentials to be forwarded to the
remote machine for use by the specified [4mcommand[24m. They will be
removed when [4mcommand[24m finishes. This option is mutually exclu-
sive with the [1m-f [22moption.
[1m-k [4m[22mrealm[0m
causes [4mrsh[24m to obtain tickets for the remote host in [4mrealm[0m
instead of the remote host's realm as determined by [4mkrb_real-[0m
[4mmofhost[24m(3).
[1m-d [22mturns on socket debugging (via [4msetsockopt[24m(2)) on the TCP sockets
used for communication with the remote host.
[1m-n [22mredirects input from the special device [4m/dev/null[24m (see the BUGS
section below).
Shell metacharacters which are not quoted are interpreted on the local
machine, while quoted metacharacters are interpreted on the remote
machine. Thus the command
rsh otherhost cat remotefile >> localfile
appends the remote file [4mremotefile[24m to the local file [4mlocalfile[24m, while
rsh otherhost cat remotefile ">>" otherremotefile
appends [4mremotefile[24m to [4motherremotefile[24m.
[1mFILES[0m
/etc/hosts
~/.k5login (on remote host) - file containing Kerberos principals that
are allowed access.
[1mSEE ALSO[0m
rlogin(1), kerberos(3), krb_sendauth(3), krb_realmofhost(3), kshd(8)
[1mBUGS[0m
If you are using [4mcsh[24m(1) and put a [4mrsh[24m(1) 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 [4mrsh[24m to /dev/null using the [1m-n [22moption.
You cannot run an interactive command (like [4mrogue[24m(6) or [4mvi[24m(1)); use
[4mrlogin[24m(1).
Stop signals stop the local [4mrsh[24m process only; this is arguably wrong,
but currently hard to fix for reasons too complicated to explain here.
RSH(1)
Man(1) output converted with
man2html