HP Workstation zx2000 HP Graphics Administration Guide for HP-UX 11.X (IPF ver - Page 41

signals, starting the X Server from the command line, Description

Page 41 highlights

configuring an X Server on HP-UX For example: joesworkstation corporate.company.com star:: bigcpu:: Users can add or remove hosts from this list and enable or disable access control using the xhost command from the same machine as the server. The X protocol intrinsically does not have any notion of window operation permissions or place any restrictions on what a client can do; if a program can connect to a display, it has full run of the screen. X Servers that support the SECURITY extension fare better because clients can be designated untrusted via the authorization they use to connect; see the xauth(1) manual page for details. Restrictions are imposed on untrusted clients that curtail the mischief they can do. See the SECURITY extension specification for a complete list of these restrictions. Sites that have better authentication and authorization systems might wish to make use of the hooks in the libraries and the server to provide additional security models. signals This entire section comes from XFree86 Xserver(1) manual page. The X Server attaches special meaning to the signals in the following table. Signal Description Signals SIGHUP Causes the server to close all existing connections, free all resources, and restore all defaults. It is sent by the display manager whenever the main user's main application (usually an xterm or window manager) exits to force the server to clean up and prepare for the next user. SIGTERM Causes the server to exit cleanly. SIGUSR1 Used quite differently from either of the above. When the server starts, it checks to see if it has inherited SIGUSR1 as SIG_IGN instead of the usual SIG_DFL. In this case, the server sends a SIGUSR1 to its parent process after it has set up the various connection schemes. Xdm uses this feature to recognize when connecting to the server is possible. starting the X Server from the command line Starting X from the command line is not the preferred method of starting X on HP-UX. This documentation outlines the necessary steps to start X from the command line and the command line options for those users who may need to do so. The documentation provided here is based on the Xf86(1) manual page. Itanium systems support two distinct X Servers. The display server is based on XFree86 and is in /usr/bin/X11/Xf86. The Technical Print Server (TPS) is based on HP's X Server and is in /usr/bin/X11/Xhp. The desktop wants to invoke the X Server as /usr/bin/X11/X. To solve the problem of needing to be able to invoke either of the X Servers, an X loader has been added in /usr/bin/X11/X. The X loader is responsible for deciding which X server to invoke. When the X loader starts one of the X Servers, it passes all the arguments to the X Server. The following example demonstrates how to start the Xserver from the command line. Graphics Administration Guide 4-29

  • 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
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66

Graphics Administration Guide
4–29
configuring an X Server on HP-UX
For example:
joesworkstation
corporate.company.com
star::
bigcpu::
Users can add or remove hosts from this list and enable or disable access control using the
xhost
command from the same machine as the server.
The X protocol intrinsically does not have any notion of window operation permissions or place
any restrictions on what a client can do; if a program can connect to a display, it has full run of
the screen. X Servers that support the SECURITY extension fare better because clients can be
designated untrusted via the authorization they use to connect; see the
xauth(1)
manual page
for details. Restrictions are imposed on untrusted clients that curtail the mischief they can do. See
the SECURITY extension specification for a complete list of these restrictions.
Sites that have better authentication and authorization systems might wish to make use of the
hooks in the libraries and the server to provide additional security models.
signals
This entire section comes from
XFree86 Xserver(1)
manual page.
The X Server attaches special meaning to the signals in the following table.
starting the X Server from the command line
Starting X from the command line is not the preferred method of starting X on HP-UX. This
documentation outlines the necessary steps to start X from the command line and the command
line options for those users who may need to do so. The documentation provided here is based on
the
Xf86(1)
manual page.
Itanium systems support two distinct X Servers. The display server is based on XFree86 and is in
/usr/bin/X11/Xf86
. The Technical Print Server (TPS) is based on HP’s X Server and is in
/usr/bin/X11/Xhp
. The desktop wants to invoke the X Server as
/usr/bin/X11/X
. To
solve the problem of needing to be able to invoke either of the X Servers, an X loader has been
added in
/usr/bin/X11/X
. The X loader is responsible for deciding which X server to
invoke. When the X loader starts one of the X Servers, it passes all the arguments to the X Server.
The following example demonstrates how to start the Xserver from the command line.
Signals
Signal
Description
SIGHUP
Causes the server to close all existing connections, free all resources, and restore
all defaults. It is sent by the display manager whenever the main user's main
application (usually an xterm or window manager) exits to force the server to
clean up and prepare for the next user.
SIGTERM
Causes the server to exit cleanly.
SIGUSR1
Used quite differently from either of the above. When the server starts, it checks
to see if it has inherited SIGUSR1 as SIG_IGN instead of the usual SIG_DFL. In
this case, the server sends a SIGUSR1 to its parent process after it has set up the
various connection schemes. Xdm uses this feature to recognize when connecting
to the server is possible.