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
47RSTART(1)                   General Commands Manual                  RSTART(1)
48
49
50

NAME

52       rstart - a sample implementation of a Remote Start client
53

SYNOPSIS

55       rstart [-c context] [-g] [-l username] [-v] hostname command args ...
56

DESCRIPTION

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

OPTIONS

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

NOTES

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

SEE ALSO

119       rstartd(1), rsh(1), A Flexible Remote Execution Protocol Based on rsh
120

AUTHOR

122       Jordan Brown, Quarterdeck Office Systems
123
124
125
126X Version 11                     rstart 1.0.2                        RSTART(1)