|
0
|
1 .TH GNUSERV 1 "" "XEmacs Server"
|
|
|
2 .UC 4
|
|
|
3 .SH NAME
|
|
163
|
4 gnuserv, gnuclient \- Server and Clients for XEmacs
|
|
0
|
5 .SH SYNOPSIS
|
|
|
6 .B gnuclient
|
|
181
|
7 [-nw] [-display display] [-q] [-v] [-l library] [-batch] [-f function] [-eval form]
|
|
|
8 [-h hostname] [-p port] [-r remote-pathname] [[+line] file] ...
|
|
|
9 .br
|
|
|
10 .B gnudoit [-q]
|
|
|
11 form
|
|
0
|
12 .br
|
|
|
13 .B gnuserv
|
|
181
|
14 .br
|
|
|
15 .B gnuattach
|
|
|
16 Removed as of gnuserv 3.x
|
|
0
|
17 .SH DESCRIPTION
|
|
|
18
|
|
|
19 .PP
|
|
163
|
20 \fIgnuclient\fP allows the user to request a running XEmacs process to
|
|
181
|
21 edit the named files or directories and/or evaluate lisp forms.
|
|
|
22 Depending on your environment, it can be an X frame or a TTY frame.
|
|
|
23 One typical use for this is with a dialup connection to a machine on
|
|
|
24 which an XEmacs process is currently running.
|
|
|
25 .PP
|
|
|
26 \fIgnudoit\fP is a shell script frontend to ``gnuclient -batch -eval form''.
|
|
|
27 Its use is depreciated. Try to get used to calling gnuclient directly.
|
|
0
|
28 .PP
|
|
163
|
29 \fIgnuserv\fP is the server program that is set running by XEmacs to
|
|
|
30 handle all incoming and outgoing requests. It is not usually invoked
|
|
|
31 directly, but is started from XEmacs by loading the \fIgnuserv\fP
|
|
|
32 package and evaluating the Lisp form (gnuserv-start).
|
|
181
|
33 .PP
|
|
|
34 \fIgnuattach\fP no longer exists. Its functionality has been replaced by
|
|
|
35 \fIgnuclient -nw\fP.
|
|
0
|
36 .SH OPTIONS
|
|
181
|
37 .PP
|
|
|
38 \fIgnuclient\fP supports as much of the command line options of Emacs as
|
|
|
39 makes sense in this context. In addition it adds a few of its own.
|
|
|
40 .br
|
|
|
41 Options with long names can also be specified using a double
|
|
|
42 hyphen instead of a single one.
|
|
|
43 .TP 8
|
|
|
44 .BI \-nw
|
|
|
45 This option makes \fIgnuclient\fP act as a frontend such that XEmacs
|
|
|
46 can attach to the current TTY. XEmacs will then open a new TTY frame.
|
|
|
47 The effect is similar to having started a new XEmacs on this TTY with
|
|
|
48 the ``-nw'' option. It currently only works if XEmacs is running on
|
|
|
49 the same machine as gnuclient. This is the default if the `DISPLAY'
|
|
|
50 environment variable is not set.
|
|
|
51 .TP 8
|
|
|
52 .BI \-display " display, " \--display " display"
|
|
|
53 If this option is given or the `DISPLAY' environment variable is set
|
|
|
54 then gnuclient will tell XEmacs to edit files in a frame on the
|
|
|
55 specified X device.
|
|
0
|
56 .TP 8
|
|
|
57 .BI \-q
|
|
163
|
58 This option informs \fIgnuclient\fP to exit once connection has been
|
|
|
59 made with the XEmacs process. Normally \fIgnuclient\fP waits until
|
|
|
60 all of the files on the command line have been finished with (their
|
|
|
61 buffers killed) by the XEmacs process, and all the forms have been
|
|
|
62 evaluated.
|
|
0
|
63 .TP 8
|
|
181
|
64 .BI \-v
|
|
|
65 When this option is specified \fIgnuclient\fP will request for the
|
|
|
66 specified files to be viewed instead of edited.
|
|
|
67 .TP 8
|
|
|
68 .BI \-l " library"
|
|
|
69 Tell Emacs to load the specified library.
|
|
|
70 .TP 8
|
|
|
71 .BI \-batch
|
|
|
72 Tell Emacs not to open any frames. Just load libraries and evaluate lisp code. You
|
|
|
73 must use the
|
|
|
74 .BR \-l ,
|
|
|
75 .BR \-f ,
|
|
|
76 and
|
|
|
77 .B \-eval
|
|
|
78 options to specify files to execute and functions to call.
|
|
|
79 .TP 8
|
|
|
80 .BI \-f " function,"
|
|
|
81 Make Emacs execute the lisp function.
|
|
|
82 .TP 8
|
|
|
83 .BI \-eval " form"
|
|
|
84 Make Emacs execute the lisp form.
|
|
|
85 .TP 8
|
|
0
|
86 .BI \-h " hostname"
|
|
|
87 Used only with Internet-domain sockets, this option specifies the host
|
|
181
|
88 machine which should be running \fIgnuserv\fP. If this option is not
|
|
0
|
89 specified then the value of the environment variable GNU_HOST is used
|
|
181
|
90 if set. If no hostname is specified, and the GNU_HOST variable is not
|
|
|
91 set, an internet connection will not be attempted. N\.B.:
|
|
|
92 \fIgnuserv\fP does NOT allow internet connections unless XAUTH
|
|
|
93 authentication is used or the GNU_SECURE variable has been specified
|
|
|
94 and points at a file listing all trusted hosts. (See SECURITY below.)
|
|
0
|
95
|
|
|
96 .br
|
|
163
|
97 Note that an internet address may be specified instead of a hostname
|
|
|
98 which can speed up connections to the server by quite a bit,
|
|
|
99 especially if the client machine is running YP.
|
|
0
|
100
|
|
|
101 .br
|
|
|
102 Note also that a hostname of \fBunix\fP can be used to specify that
|
|
|
103 the connection to the server should use a Unix-domain socket (if
|
|
|
104 supported) rather than an Internet-domain socket.
|
|
|
105 .TP 8
|
|
|
106 .BI \-p " port"
|
|
|
107 Used only with Internet-domain sockets, this option specifies the
|
|
|
108 service port used to communicate between server and clients. If this
|
|
|
109 option is not specified, then the value of the environment variable
|
|
|
110 GNU_PORT is used, if set, otherwise a service called ``gnuserv'' is
|
|
|
111 looked up in the services database. Finally, if no other value can be
|
|
|
112 found for the port, then a default port is used which is usually 21490
|
|
|
113 + uid.
|
|
|
114 .br
|
|
|
115 Note that since \fIgnuserv\fP doesn't allow command-line options, the port for
|
|
|
116 it will have to be specified via one of the alternative methods.
|
|
|
117 .TP 8
|
|
|
118 .BI \-r " pathname"
|
|
|
119 Used only with Internet-domain sockets, the pathname argument may be
|
|
|
120 needed to inform XEmacs how to reach the root directory of a remote
|
|
163
|
121 machine. \fIgnuclient\fP prepends this string to each path argument
|
|
|
122 given. For example, if you were trying to edit a file on a client
|
|
|
123 machine called otter, whose root directory was accessible from the
|
|
|
124 server machine via the path /net/otter, then this argument should be
|
|
|
125 set to '/net/otter'. If this option is omitted, then the value is
|
|
|
126 taken from the environment variable GNU_NODE, if set, or the empty
|
|
|
127 string otherwise.
|
|
0
|
128 .TP 8
|
|
181
|
129 .BI "[+n] file"
|
|
0
|
130 This is the path of the file to be edited. If the file is a directory, then
|
|
|
131 the directory browsers dired or monkey are usually invoked instead.
|
|
181
|
132 The cursor is put at line number 'n' if specified.
|
|
0
|
133
|
|
|
134 .SH SETUP
|
|
|
135 \fIgnuserv\fP is packaged standardly with recent versions of XEmacs.
|
|
|
136 Therefore, you should be able to start the server simply by evaluating
|
|
|
137 the XEmacs Lisp form (gnuserv-start), or equivalently by typing
|
|
|
138 `M-x gnuserv-start'.
|
|
181
|
139
|
|
|
140 .SH CONFIGURATION
|
|
|
141 The behavior of this suite of program is mostly controlled on the lisp
|
|
|
142 side in Emacs and its behavior can be customized to a large extent.
|
|
|
143 Type `M-x customize-group RET gnuserv RET' for easy access. More
|
|
|
144 documentation can be found in the file `gnuserv.el'
|
|
|
145
|
|
0
|
146 .SH EXAMPLE
|
|
|
147 .RS 4
|
|
163
|
148 gnuclient -q -f mh-smail
|
|
0
|
149 .br
|
|
|
150 gnuclient -h cuckoo -r /ange@otter: /tmp/*
|
|
|
151 .br
|
|
163
|
152 gnuclient -nw ../src/listproc.c
|
|
0
|
153 .RE
|
|
181
|
154 .br
|
|
|
155
|
|
|
156 .br
|
|
|
157 More examples and sample wrapper scripts are provided in the
|
|
|
158 etc/gnuserv directory of the Emacs installation.
|
|
|
159
|
|
0
|
160
|
|
163
|
161 .SH SYSV IPC
|
|
|
162 SysV IPC is used to communicate between \fIgnuclient\fP and
|
|
|
163 \fIgnuserv\fP if the symbol SYSV_IPC is defined at the top of
|
|
|
164 gnuserv.h. This is incompatible with both Unix-domain and
|
|
|
165 Internet-domain socket communication as described below. A file called
|
|
|
166 /tmp/gsrv??? is created as a key for the message queue, and if removed
|
|
|
167 will cause the communication between server and client to fail until
|
|
|
168 the server is restarted.
|
|
0
|
169 .SH UNIX-DOMAIN SOCKETS
|
|
163
|
170 A Unix-domain socket is used to communicate between \fIgnuclient\fP
|
|
|
171 and \fIgnuserv\fP if the symbol UNIX_DOMAIN_SOCKETS is defined at the
|
|
|
172 top of gnuserv.h. A file called /tmp/gsrvdir????/gsrv is created for
|
|
|
173 communication and if deleted will cause communication between server
|
|
|
174 and client to fail. Only the user running gnuserv will be able to
|
|
|
175 connect to the socket.
|
|
0
|
176 .SH INTERNET-DOMAIN SOCKETS
|
|
|
177 Internet-domain sockets are used to communicate between
|
|
163
|
178 \fIgnuclient\fP and \fIgnuserv\fP if the symbol
|
|
|
179 INTERNET_DOMAIN_SOCKETS is defined at the top of gnuserv.h. Both
|
|
|
180 Internet-domain and Unix-domain sockets can be used at the same
|
|
|
181 time. If a hostname is specified via -h or via the GNU_HOST
|
|
|
182 environment variable, \fIgnuclient\fP establish connections using an
|
|
|
183 internet domain socket. If not, a local connection is attempted via
|
|
|
184 either a unix-domain socket or SYSV IPC.
|
|
0
|
185 .SH SECURITY
|
|
|
186 Using Internet-domain sockets, a more robust form of security is
|
|
|
187 needed that wasn't necessary with either Unix-domain sockets or SysV
|
|
|
188 IPC. Currently, two authentication protocols are supported to provide
|
|
|
189 this: MIT-MAGIC-COOKIE-1 (based on the X11 xauth(1) program) and a
|
|
|
190 simple host-based access control mechanism, hereafter called
|
|
|
191 GNUSERV-1. The GNUSERV-1 protocol is always available, whereas support
|
|
|
192 for MIT-MAGIC-COOKIE-1 may or may not have been enabled (via a #define
|
|
|
193 at the top of gnuserv.h) at compile-time.
|
|
|
194 .PP
|
|
|
195 \fIgnuserv\fP, using GNUSERV-1, performs a limited form of access
|
|
|
196 control at the machine level. By default no internet-domain socket is
|
|
|
197 opened. If the variable GNU_SECURE can be found in \fIgnuserv\fP's
|
|
|
198 environment, and it names a readable filename, then this file is
|
|
|
199 opened and assumed to be a list of hosts, one per line, from which the
|
|
|
200 server will allow requests. Connections from any other host will be
|
|
|
201 rejected. Even the machine on which \fIgnuserv\fP is running is not
|
|
|
202 permitted to make connections via the internet socket unless its
|
|
|
203 hostname is explicitly specified in this file. Note that a host may
|
|
|
204 be either a numeric IP address or a hostname, and that
|
|
|
205 .I any
|
|
|
206 user on an approved host may connect to your gnuserv and execute arbitrary
|
|
|
207 elisp (e.g., delete all your files).
|
|
|
208 If this file contains a lot of
|
|
|
209 hostnames then the server may take quite a time to start up.
|
|
|
210 .PP
|
|
|
211 When the MIT-MAGIC-COOKIE-1 protocol is enabled, an internet socket
|
|
|
212 \fIis\fP opened by default. \fIgnuserv\fP will accept a connection from
|
|
|
213 any host, and will wait for a "magic cookie" (essentially, a password)
|
|
|
214 to be presented by the client. If the client doesn't present the
|
|
|
215 cookie, or if the cookie is wrong, the authentication of the client is
|
|
|
216 considered to have failed. At this point. \fIgnuserv\fP falls back to
|
|
|
217 the GNUSERV-1 protocol; If the client is calling from a host listed in
|
|
|
218 the GNU_SECURE file, the connection will be accepted, otherwise it
|
|
|
219 will be rejected.
|
|
|
220 .TP 4
|
|
|
221 .I Using MIT-MAGIC-COOKIE-1 authentication
|
|
|
222 When the \fIgnuserv\fP server is started, it looks for a cookie
|
|
|
223 defined for display 999 on the machine where it is running. If the
|
|
|
224 cookie is found, it will be stored for use as the authentication
|
|
|
225 cookie. These cookies are defined in an authorization file (usually
|
|
|
226 ~/.Xauthority) that is manipulated by the X11 xauth(1) program. For
|
|
|
227 example, a machine "kali" which runs an emacs that invokes
|
|
|
228 \fIgnuserv\fP should respond as follows (at the shell prompt) when set
|
|
|
229 up correctly.
|
|
|
230 .PP
|
|
|
231 .RS 8
|
|
|
232 kali% xauth list
|
|
|
233 .br
|
|
|
234 GS65.SP.CS.CMU.EDU:0 MIT-MAGIC-COOKIE-1 11223344
|
|
|
235 .br
|
|
|
236 KALI.FTM.CS.CMU.EDU:999 MIT-MAGIC-COOKIE-1 1234
|
|
|
237 .RE
|
|
|
238 .PP
|
|
|
239 .RS 4
|
|
|
240 In the above case, the authorization file defines two cookies. The
|
|
|
241 second one, defined for screen 999 on the server machine, is used for
|
|
|
242 gnuserv authentication.
|
|
|
243 .PP
|
|
|
244 On the client machine's side, the authorization file must contain an
|
|
|
245 identical line, specifying the
|
|
|
246 .I server's
|
|
|
247 cookie. In other words, on a machine "foobar" which wishes to connect
|
|
|
248 to "kali," the `xauth list' output should contain the line:
|
|
|
249 .PP
|
|
|
250 .RS 4
|
|
|
251 KALI.FTM.CS.CMU.EDU:999 MIT-MAGIC-COOKIE-1 1234
|
|
|
252 .RE
|
|
|
253 .PP
|
|
|
254 For more information on authorization files, take a look at the
|
|
|
255 xauth(1X11) man page, or invoke xauth interactively (without any
|
|
|
256 arguments) and type "help" at the prompt. Remember that case in the
|
|
|
257 name of the authorization protocol (i.e.`MIT-MAGIC-COOKIE-1')
|
|
|
258 .I is
|
|
|
259 significant!
|
|
|
260 .RE
|
|
|
261
|
|
181
|
262
|
|
|
263 .SH ENVIRONMENT
|
|
|
264 .PP
|
|
|
265 .TP 8
|
|
|
266 .B DISPLAY
|
|
|
267 Default X device to put edit frame.
|
|
|
268
|
|
0
|
269 .SH FILES
|
|
|
270 .PP
|
|
|
271 .TP 8
|
|
|
272 .B /tmp/gsrv???
|
|
|
273 (SYSV_IPC only)
|
|
|
274 .TP 8
|
|
|
275 .B /tmp/gsrvdir???/gsrv
|
|
|
276 (unix domain sockets only)
|
|
|
277 .TP 8
|
|
|
278 .B ~/.emacs
|
|
|
279 XEmacs customization file, see xemacs(1).
|
|
|
280 .SH SEE ALSO
|
|
|
281 .PP
|
|
|
282 .TP 8
|
|
181
|
283 xauth(1X11), Xsecurity(1X11), gnuserv.el
|
|
0
|
284 .SH BUGS
|
|
|
285 .PP
|
|
|
286 NULs occurring in result strings don't get passed back to gnudoit properly.
|
|
|
287
|
|
|
288 .SH AUTHOR.
|
|
|
289 Andy Norman (ange@hplb.hpl.hp.com), based heavily upon
|
|
|
290 etc/emacsclient.c, etc/server.c and lisp/server.el from the GNU Emacs
|
|
|
291 18.52 distribution. Various modifications from Bob Weiner (weiner@mot.com),
|
|
163
|
292 Darrell Kindred (dkindred@cmu.edu), Arup Mukherjee (arup@cmu.edu), Ben
|
|
|
293 Wing (wing@666.com) and Hrvoje Niksic (hniksic@srce.hr).
|
