1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50RSTART(1)                   General Commands Manual                  RSTART(1)
51
52
53

NAME

55       rstart - a sample implementation of a Remote Start client
56

SYNOPSIS

58       rstart [-c context] [-g] [-l username] [-v] hostname command args ...
59

DESCRIPTION

61       Rstart  is  a simple implementation of a Remote Start client as defined
62       in "A Flexible Remote Execution Protocol Based on rsh".  It uses rsh as
63       its underlying remote execution mechanism.
64

OPTIONS

66       -c context
67               This option specifies the context in which the command is to be
68               run.  A context specifies a general environment the program  is
69               to  be  run  in.  The details of this environment are host-spe‐
70               cific; the intent is that the client  need  not  know  how  the
71               environment  must  be  configured.   If  omitted,  the  context
72               defaults to X.  This should be suitable for running X  programs
73               from the host's "usual" X installation.
74
75       -g      Interprets  command  as  a generic command, as discussed in the
76               protocol document.  This is intended to allow  common  applica‐
77               tions to be invoked without knowing what they are called on the
78               remote system.  Currently, the only  generic  commands  defined
79               are  Terminal,  LoadMonitor,  ListContexts, and ListGenericCom‐
80               mands.
81
82       -l username
83               This option is passed to the underlying rsh; it  requests  that
84               the command be run as the specified user.
85
86       -v      This  option  requests that rstart be verbose in its operation.
87               Without this option, rstart discards output from  the  remote's
88               rstart helper, and directs the rstart helper to detach the pro‐
89               gram from the rsh connection  used  to  start  it.   With  this
90               option, responses from the helper are displayed and the result‐
91               ing program is not detached from the connection.
92

NOTES

94       This is a trivial implementation.  Far more  sophisticated  implementa‐
95       tions are possible and should be developed.
96
97       Error  handling  is  nonexistent.   Without  -v, error reports from the
98       remote are discarded silently.  With -v, error reports are displayed.
99
100       The $DISPLAY environment variable is  passed.   If  it  starts  with  a
101       colon,  the  local hostname is prepended.  The local domain name should
102       be appended to unqualified host names, but isn't.
103
104       The $SESSION_MANAGER environment variable should be passed, but isn't.
105
106       X11 authority information is passed for the current display.
107
108       ICE authority information should be passed, but isn't.  It  isn't  com‐
109       pletely  clear  how rstart should select what ICE authority information
110       to pass.
111
112       Even without -v, the sample rstart helper will leave  a  shell  waiting
113       for  the  program  to  complete.  This causes no real harm and consumes
114       relatively few resources, but if it is undesirable it can be avoided by
115       explicitly specifying the "exec" command to the shell, eg
116       rstart somehost exec xterm
117       This  is  obviously  dependent on the command interpreter being used on
118       the remote system; the example given will work for  the  Bourne  and  C
119       shells.
120

SEE ALSO

122       rstartd(1), rsh(1), A Flexible Remote Execution Protocol Based on rsh
123

AUTHOR

125       Jordan Brown, Quarterdeck Office Systems
126
127
128
129X Version 11                     rstart 1.0.2                        RSTART(1)