⟦7e5db6b26⟧

TextFile

.TH X 8C "25 January 1986" "X Version 10"
.SH NAME
X - X window system server
.SH SYNOPSIS
.B X
<display> [ option ... ] <tty>
.SH DESCRIPTION
.I X
is the window system server.
It is normally run automatically by \fIinit(8)\fP,
which provides the tty argument.
The display argument is the number of the bitmap display to service.
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.
.PP
The program \fIxinit(8)\fP is  usually used to start
X interactively.
.PP
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 \fI/dev/X*\fP,
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.
.SH
OPTIONS
.PP
See the \fIX(1)\fP manual page for a list of command line options.
.SH
INITIALIZATION
.PP
\fIX(1)\fP and your first \fIxterm(1)\fP are normally started by the 
\fIinit(8)\fP program.
.sp
A typical line in \fI/etc/ttys\fP might be:
.sp
.nf
	ttyv0 "/etc/xterm -L =-1+1 :0" xterm on secure window="/etc/Xvs100 0 -c -l"
.fi
.sp
However, if you want the xterm to run on a different machine, you might have:
.sp
.nf
	remote "/etc/X 0 -l -c" xterm on secure
.fi
.sp
on the server machine and
.sp
.nf
	ttyv0 "/exe/xterm -L =-1+1 orpheus:0" xterm on secure
.fi
.sp
on the client machine.
.sp
.I X
maintains an access control list for accepting connections.  The host where
the server runs is initially on the list.
In addition, hosts listed the file
\fI/etc/X*.hosts\fP,
where \fI*\fP 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 \fIxhost(1)\fP.
.sp
.I X
will catch the SIGHUP signal sent by \fIinit(8)\fP
after the initial process (usually
the login \fIxterm(1)\fP) 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.
.sp
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.
.SH "SEE ALSO"
X(1), xinit(1), xterm(1), bitmap(1), xwm(1), xhost(1), xload(1), xset(1), qv(4), vs(4), init(8)
.SH DIAGNOSTICS
Are too numerous to list them all.
If run from \fIinit(8)\fP, errors are logged in the file \fI/usr/adm/X*msgs\fP,
where * is the display number.  Otherwise, errors go to error output.
.sp
`fatal error: No such device or address at Opening' usually means
someone else (like an existing X) has the display open.
.sp
`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.
.SH FILES
.ta \w'/usr/new/lib/X/s-code   'u
/etc/X*.hosts	Initial access control list
.br
/usr/new/lib/X/font	VS100/QVSS font directory
.br
/usr/new/lib/X/s-code	VS100 firmware directory
.br
/dev/vs*	VS100 devices
.br
/dev/qd*	QDSS devices
.br
/dev/mouse	QVSS device
.br
/dev/X*	Unix domain socket (if configured)
.br
/usr/adm/X*msgs	Error log file
.SH BUGS
The option syntax is inconsistent with itself and \fIxset(1)\fP.
.sp
If
.I X
dies before its clients, new clients won't be able to connect until all
existing connections have their TCP TIME_WAIT timers expire.
.SH AUTHOR
Bob Scheifler (MIT-LCS).
.br
Copyright (c) 1984, 1985, 1986, by Massachusetts Institute of Technology.
.br
See \fIX(1)\fP for a complete copyright notice.
DataMuseum.dk

DKUUG/EUUG Conference tapes

⟦7e5db6b26⟧ TextFile

Derivation

TextFile
