4.3BSD-UWisc/man/cat8/X.8c
X(8C) UNIX Programmer's Manual X(8C)
NAME
X - X window system server
SYNOPSIS
X <display> [ option ... ] <tty>
DESCRIPTION
_X is the window system server. It is normally run automati-
cally by _i_n_i_t(_8), which provides the tty argument. The
display argument is the number of the bitmap display to ser-
vice. The number is typically in the range 0-6, and defines
the ports the server will accept connections on and the
filename of the device.
The program _x_i_n_i_t(_8) is usually used to start X interac-
tively.
Connections through the Unix domain, through TCP, and
through DECnet are currently possible. The connections
actually accepted by a server depend on how it was compiled.
Unix domain connections are through /_d_e_v/_X*, where * is the
display number. TCP connections are through ports 5800+N
(VAX byte order) and 5900+N (68000 byte order), where N is
the display number. DECnet connections are through object
name ``X*'', where * is the display number.
OPTIONS
See the _X(_1) manual page for a list of command line options.
INITIALIZATION
_X(_1) and your first _x_t_e_r_m(_1) are normally started by the
_i_n_i_t(_8) program.
A typical line in /_e_t_c/_t_t_y_s might be:
ttyv0 "/etc/xterm -L =-1+1 :0" xterm on secure window="/etc/Xvs100 0 -c -l"
However, if you want the xterm to run on a different
machine, you might have:
remote "/etc/X 0 -l -c" xterm on secure
on the server machine and
ttyv0 "/exe/xterm -L =-1+1 orpheus:0" xterm on secure
on the client machine.
Printed 1/10/87 25 January 1986 1
X(8C) UNIX Programmer's Manual X(8C)
_X maintains an access control list for accepting connec-
tions. The host where the server runs is initially on the
list. In addition, hosts listed the file /_e_t_c/_X*._h_o_s_t_s,
where * is the display number, are also initially on the
list. The format of this file is a list of host names, one
per line. DECnet hosts are distinguished from Internet
hosts by the existance of a trailing ``::'' in the name. The
access control list can be manipulated with _x_h_o_s_t(_1).
_X will catch the SIGHUP signal sent by _i_n_i_t(_8) after the
initial process (usually the login _x_t_e_r_m(_1)) started on the
display terminates. This signal causes all connections to
be closed (thereby ``disowning'' the terminal), all
resources to be freed, and all defaults restored.
The X protocol is documented in ``X.doc''. Note that while
X is running, all access to the display must be through the
window system.
SEE ALSO
X(1), xinit(1), xterm(1), bitmap(1), xwm(1), xhost(1),
xload(1), xset(1), qv(4), vs(4), init(8)
DIAGNOSTICS
Are too numerous to list them all. If run from _i_n_i_t(_8),
errors are logged in the file /_u_s_r/_a_d_m/_X*_m_s_g_s, where * is
the display number. Otherwise, errors go to error output.
`fatal error: No such device or address at Opening' usually
means someone else (like an existing X) has the display
open.
`fatal error: No such file or directory at Initializing'
usually means the VS100 firmware was not found or that the
device file for the display does not exist.
FILES
/etc/X*.hosts Initial access control list
/usr/new/lib/X/font VS100/QVSS font directory
/usr/new/lib/X/s-code VS100 firmware directory
/dev/vs* VS100 devices
/dev/qd* QDSS devices
/dev/mouse QVSS device
/dev/X* Unix domain socket (if configured)
/usr/adm/X*msgs Error log file
BUGS
The option syntax is inconsistent with itself and _x_s_e_t(_1).
If _X dies before its clients, new clients won't be able to
connect until all existing connections have their TCP
TIME_WAIT timers expire.
Printed 1/10/87 25 January 1986 2
X(8C) UNIX Programmer's Manual X(8C)
AUTHOR
Bob Scheifler (MIT-LCS).
Copyright (c) 1984, 1985, 1986, by Massachusetts Institute
of Technology.
See _X(_1) for a complete copyright notice.
Printed 1/10/87 25 January 1986 3