1RSH(1)                    BSD General Commands Manual                   RSH(1)
2

NAME

4     rsh — remote shell
5

SYNOPSIS

7     rsh [-Kdnx] [-l username] host [command]
8

DESCRIPTION

10     Rsh executes command on host.
11
12     Rsh copies its standard input to the remote command, the standard output
13     of the remote command to its standard output, and the standard error of
14     the remote command to its standard error.  Interrupt, quit and terminate
15     signals are propagated to the remote command; rsh normally terminates
16     when the remote command does.  The options are as follows:
17
18     -d    The -d option turns on socket debugging (using setsockopt(2)) on
19           the TCP sockets used for communication with the remote host.
20
21     -l    By default, the remote username is the same as the local username.
22           The -l option allows the remote name to be specified.
23
24     -n    The -n option redirects input from the special device /dev/null
25           (see the BUGS section of this manual page).
26
27     If no command is specified, you will be logged in on the remote host
28     using rlogin(1).
29
30     Shell metacharacters which are not quoted are interpreted on local
31     machine, while quoted metacharacters are interpreted on the remote
32     machine.  For example, the command
33
34           rsh otherhost cat remotefile >> localfile
35
36     appends the remote file remotefile to the local file localfile, while
37
38           rsh otherhost cat remotefile ">>" other_remotefile
39
40     appends remotefile to other_remotefile.
41

FILES

43     /etc/hosts
44

SEE ALSO

46     rlogin(1),
47

HISTORY

49     The rsh command appeared in 4.2BSD.
50

BUGS

52     If you are using csh(1) and put a rsh in the background without redirect‐
53     ing its input away from the terminal, it will block even if no reads are
54     posted by the remote command.  If no input is desired you should redirect
55     the input of rsh to /dev/null using the -n option.
56
57     You cannot run an interactive command (like rogue(6) or vi(1)) using rsh;
58     use rlogin(1) instead.
59
60     Stop signals stop the local rsh process only; this is arguably wrong, but
61     currently hard to fix for reasons too complicated to explain here.
62
63Linux NetKit (0.17)             August 15, 1999            Linux NetKit (0.17)
Impressum