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
33RSTART(1)                   General Commands Manual                  RSTART(1)
34
35
36

NAME

38       rstart - a sample implementation of a Remote Start client
39

SYNOPSIS

41       rstart [-c context] [-g] [-l username] [-v] hostname command args ...
42

DESCRIPTION

44       Rstart  is  a simple implementation of a Remote Start client as defined
45       in "A Flexible Remote Execution Protocol Based on rsh".  It uses rsh as
46       its underlying remote execution mechanism.
47

OPTIONS

49       -c context
50               This option specifies the context in which the command is to be
51               run.  A context specifies a general environment the program  is
52               to  be  run  in.  The details of this environment are host-spe‐
53               cific; the intent is that the client need not know how the  en‐
54               vironment must be configured.  If omitted, the context defaults
55               to X.  This should be suitable for running X programs from  the
56               host's "usual" X installation.
57
58       -g      Interprets  command  as  a generic command, as discussed in the
59               protocol document.  This is intended to allow  common  applica‐
60               tions to be invoked without knowing what they are called on the
61               remote system.  Currently, the only  generic  commands  defined
62               are  Terminal,  LoadMonitor,  ListContexts, and ListGenericCom‐
63               mands.
64
65       -l username
66               This option is passed to the underlying rsh; it  requests  that
67               the command be run as the specified user.
68
69       -v      This  option  requests that rstart be verbose in its operation.
70               Without this option, rstart discards output from  the  remote's
71               rstart helper, and directs the rstart helper to detach the pro‐
72               gram from the rsh connection used to start it.  With  this  op‐
73               tion, responses from the helper are displayed and the resulting
74               program is not detached from the connection.
75

NOTES

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

SEE ALSO

105       rstartd(1), rsh(1), A Flexible Remote Execution Protocol Based on rsh
106

AUTHOR

108       Jordan Brown, Quarterdeck Office Systems
109
110
111
112X Version 11                     rstart 1.0.2                        RSTART(1)