| Previous | Contents | Index |
The following sections describe features that pertain to managing the
DECwindows X11 Display Server.
3.7.1 New Server Parameter for Setting Process Priority
V1.3--1
The DECW$SERVER_PRIORITY parameter controls the priority of the X display server process. This parameter enables you to reduce the priority of the server process and improve system performance in request-intensive situations where response time is sluggish.
Some client applications send continuous requests that do not require a reply to the X display server. These request can impact the processing time allocated to other applications. This can sometimes slow the response time of applications such as the Window Manager so significantly that they appear locked.
To set the priority of the server process, do the following:
$ DECW$SERVER_PRIORITY == "4" |
V1.3
In support of the enhanced X server device setup, keyboard, security, and error reporting capabilities provided with the X11R6.6 upgrade, the following parameters have been added to the DECW$PRIVATE_SERVER_SETUP.COM file:
| Parameter | Type | Default Value | Range |
|---|---|---|---|
| DECW$SECURITY_POLICY | String | ||
| DECW$SERVER_ACCESS_TRUSTED | String | SYS$MANAGER:DECW$SERVER_ACCESS_TRUSTED.DAT | |
| DECW$SERVER_ACCESS_ALLOWED | String | SYS$MANAGER:DECW$SERVER_ACCESS_ALLOWED.DAT | |
| DECW$SERVER_AUDIT_LEVEL | Integer | 0 | 0,1,2,4 |
| DECW$SERVER_DISABLESCREEN | Integer | 0...15 | |
| DECW$SERVER_DISABLE_TEST | Boolean | False | |
| DECW$SERVER_EDGE_BOTTOM | Integer list | ||
| DECW$SERVER_EDGE_LEFT | Integer list | ||
| DECW$SERVER_EDGE_RIGHT | Integer list | ||
| DECW$SERVER_EDGE_TOP | Integer list | ||
| DECW$SERVER_ENABLE_ACCESSX | Boolean | 0 | |
| DECW$SERVER_ENABLESCREEN | Integer | 0...15 | |
| DECW$SERVER_EXTENSIONS | String list | XIE,DEC-XTRAP,MULTI-BUFFERING,SEC_XAG | |
| DECW$SERVER_KEY_REPEAT_DELAY | Integer | 660 | 0...1000 |
| DECW$SERVER_KEY_REPEAT_INTERVAL | Integer | 40 | 0...1000 |
| DECW$SERVER_ONLYSCREEN | Integer | 0...15 | |
| DECW$SERVER_SCREENS | String list | ||
| DECW$SERVER_XAUTHORITY | String | ||
| DECW$SERVER_XKEYBOARD_COMPILED_DIR | String list | SYS$COMMON:[SYS$KEYMAP.XKB.COMPILED] | |
| DECW$SERVER_XKEYBOARD_DIRECTORY | String list | DECW$SYSCOMMON:[SYS$KEYMAP.XKB] | |
| DECW$SERVER_XKEYBOARD_LOAD_MAP | Integer | 0 | 0...1 |
| DECW$SERVER_XKEYBOARD_MAP | String | DIGITAL_US_LK201 |
If you plan on defining any of these parameters, do one of the following:
The following sections further describe each parameter. Note that these
parameters are intended for use on or with OpenVMS Alpha Version 7.3--2
systems only. For a description of additional X server parameters, see
Managing DECwindows Motif for OpenVMS Systems.
3.7.2.1 Extension Setup
While some extensions are a permanent part of the DECwindows X11 Display Server and are always enabled, some require activation through a parameter definition. Use the new parameters described in this section to set the range of active extensions on one or more DECwindows X11 Display Server systems.
See Section 3.7.3 for instructions on how to enable one or more X server extensions. For a brief description of the new extensions available with the DECwindows X11 Display Server, see Section 4.5.1.
This parameter determines which loadable server extensions are enabled and active. The valid values for DECW$SERVER_EXTENSIONS are:
The default is "XIE,DEC-XTRAP,MULTI-BUFFERING,SEC_XAG." If you have user-written, third-party, or other HP X Window System extensions, you can use this parameter to enable the extensions at server startup.
To prevent contention over resources or server requests, some combinations of extensions should not be loaded on the same display server system. See the HP DECwindows Motif for OpenVMS Alpha Release Notes for the list of unsupported combinations of server extensions. |
The following parameter definition specifies the range of server extensions to enable:
Example
$ DECW$SERVER_EXTENSIONS == "XIE,DEC-XTRAP,XINERAMA,SEC_XAG,DBE" |
This parameter controls whether test extensions, XTEST and DEC-XTRAP, are enabled. Valid values for this parameter are T (True-disable) or F (False-enable) The default value is F.
The following parameter definition enables all test extensions:
Example
$ DECW$SERVER_DISABLE_TEST == "F" |
The XINERAMA extension (formerly known as Panoramix) is used to construct a multiheaded X Window system and have it function as a single virtual display. Use the parameters in this section to define and enable the screens in the display, control their order, and set the boundary and shape of the display.
By default, all screens in the display are enabled. You can use DECW$SERVER_ONLYSCREEN, DECW$SERVER_DISABLESCREEN to selectively remove one or more screens from the from the display. Disabled screens are not initialized and are not assigned a screen number. For instructions on how to configure a multiheaded display using extension, see Section 3.7.4. For a brief description of the XINERAMA extension, see Section 4.5.1.9.
With a multiheaded system based on the XINERAMA extension, screens are initialized in alphabetical order according to their device name versus their physical position. Use this parameter to change the order in which the screens are initialized.
The following parameter definition changes the initialization order in a four-screen multiheaded display:
Example
$ DECW$SERVER_SCREENS == "GYB0,GYA0,GYD0,GYC0" |
With a multiheaded system based on the XINERAMA extension, you can choose to re-enable disabled screens in the display individually. This parameter enables the specified screen(s). The valid value ranges from 0 to 15, which represent the maximum number of screens supported by XINERAMA.
The following example enables the second screen (1) in a four-screen (0,1,2,3) multiheaded display:
Example
$ DECW$SERVER_ENABLESCREEN == "1" |
With a multiheaded system based on the XINERAMA extension, you can choose to disable each screen in the display individually. This parameter disables the specified screen. The valid value ranges from 0 to 15, which represents the maximum number of screens supported by XINERAMA.
Once a screen is disabled, it is no longer initialized as part of the display and is not assigned a screen number. Note that this changes the existing screen order and alters the display of any predefined edge attachments.
The following parameter definition disables the third screen (2) in a four-screen (0,1,2,3) multiheaded display:
Example
$ DECW$SERVER_DISABLESCREEN == "2" |
With a multiheaded system based on the XINERAMA extension, you can choose to enable individual screens in the display at the exclusion of all others. This parameter explicitly enables the specified screen(s) and disables all others. The valid value ranges from 0 to 15, which represents the maximum number of screens supported by XINERAMA.
The following parameter definition enables the second screen (1) and disables all other screens (0,2,3) in a four-screen (0,1,2,3) multiheaded display:
Example
$ DECW$SERVER_ONLYSCREEN == "1" |
With a multiheaded system based on the XINERAMA extension, edge controls are used to define the boundaries of the virtual display. This parameter determines to what screen(s) the left boundary of the display is attached. The values are determined by screen number, for example:
left-screen#, index-screen#, right-screen#
where index-screen# represents the number of the screen to which you want the boundary attached, left-screen# indicates the number of the screen directly to the left of the index, and right-screen# indicates the number of the screen directly to the right of the index. Repeat this pattern for each screen you to which you want the border attached. A value of -1 equates to none.
The following parameter definition specifies the left edge of a square, four-screen display arranged in the following order:
where the left edge of the second and fourth screens (indices 1 and 3) are attached to the first and third screens (0,2):
Example
$ DECW$SERVER_EDGE_LEFT == "-1,0,-1,2" |
With a multiheaded system based on the XINERAMA extension, edge controls are used to define the boundaries of the virtual display. This parameter determines to what screen the right boundary of the display is attached. The values are determined by screen number, for example:
right-screen#, index-screen#, left-screen#
where index-screen# represents the number of the screen to which you want the boundary attached, right-screen# indicates the number of the screen directly to the right of the index, and left-screen# indicates the number of the screen directly to the left of the index. Repeat this pattern for each screen you to which you want the border attached. A value of -1 equates to none.
The following parameter definition specifies the right edge of a square, four-screen display arranged in the following order:
where the right edges of the first and third screens (indices 0 and 2) are attached to the second and fourth screens (1,3):
Example
$ DECW$SERVER_EDGE_RIGHT == "1,-1,3,-1" |
With a multiheaded system based on the XINERAMA extension, edge controls are used to define the boundaries of the virtual display. This parameter determines to what screen the top boundary of the display is attached. The values are determined by screen number, for example:
top-screen#, index-screen#, bottom-screen#
where index-screen# represents the number of the screen to which you want the boundary attached, top-screen# indicates the number of the screen directly above the index, and bottom-screen# indicates the number of the screen directly below the index. Repeat this pattern for each screen you to which you want the border attached. A value of -1 equates to none.
The following parameter definition specifies the top edge of a square, four-screen display arranged in the following order:
where the top edges of the first and second screens (indices 0 and 1) are attached to the third and fourth screens (2,3):
Example
$ DECW$SERVER_EDGE_TOP == "2,3,-1,-1" |
With a multiheaded system based on the XINERAMA extension, edge controls are used to define the boundaries of the virtual display. This parameter determines to what screen the bottom boundary of the display is attached. The values are determined by screen number, for example:
bottom-screen#, index-screen#, top-screen#
where index-screen# represents the number of the screen to which you want the boundary attached, bottom-screen# indicates the number of the screen directly below the index, and top-screen# indicates the number of the screen directly above the index. Repeat this pattern for each screen you to which you want the border attached. A value of -1 equates to none.
The following parameter definition specifies the bottom edge of a square, four-screen display arranged in the following order:
where the bottom edges of the third and fourth screens (indices 2 and 3) are attached to the first and second screens (0,1):
Example
$ DECW$SERVER_EDGE_BOTTOM == "-1,-1,0,1" |
The X Keyboard extension (XKB) provides enhanced capabilities for defining the keyboard layout and audio feedback. It is a standard extension and includes all features previously provided by the proprietary AccessX extension. Use the new parameters in this section when using XKB to specify the settings for the X Keyboard layout files.
See Section 3.5.2 for instructions on how to load X Keyboard layout files. For a brief description of the extension, see Section 4.5.1.
This parameter enables the AccessX keyboard features for disabled users, such as sticky keys or slow keys. The valid values are 0 (disabled) or 1 (enabled). The default is 0.
The following example enables the AccessX features:
Example
$ DECW$SERVER_ENABLE_ACCESSX == "1" |
DECW$SERVER_XKEYBOARD_COMPILED_DIR
When using XKB, this parameter specifies the default directory for all compiled X Keyboard files. This directory is also where the server places any keymap files that it compiles on demand. The default is SYS$COMMON:[SYS$KEYMAP.XKB.COMPILED].
The following parameter definition changes the root directory to SYS$COMMON:[SYS$KEYMAP.XKB.SERVER1]:
Example
$ DECW$SERVER_XKEYBOARD_COMPILED_DIR == "SYS$COMMON:[SYS$KEYMAP.XKB.SERVER1]" |
DECW$SERVER_XKEYBOARD_DIRECTORY
When using XKB, this parameter specifies the default root directory for all X Keyboard files. All component source X Keyboard files are stored in subdirectories under this root directory. The default is DECW$SYSCOMMON:[SYS$KEYMAP.XKB].
The following parameter definition changes the root directory to SYS$COMMON:[SYS$KEYMAP.XKB]:
Example
$ DECW$SERVER_XKEYBOARD_DIRECTORY == "SYS$COMMON:[SYS$KEYMAP.XKB]" |
DECW$SERVER_XKEYBOARD_LOAD_MAP
When using XKB, this parameter loads the X Keyboard layout specified by DECW$SERVER_XKEYBOARD_MAP. The valid values for this parameter are 0 (disabled) or 1 (enabled). The default is 0. When this parameter is disabled, the DECwindows keyboard maps are used.
The following parameter definition loads the default X Keyboard layout file:
Example
$ DECW$SERVER_XKEYBOARD_LOAD_MAP == "1" |
When using XKB, this parameter specifies the default compiled X Keyboard layout file for your keyboard. The valid values for this parameter are the names of any compiled layout files that currently exist in the area specified by DECW$SERVER_XKEYBOARD_COMPILED_DIR. The default is DIGITAL_US_LK201.
The following parameter definition changes the X Keyboard layout to an alternate keyboard layout:
Example
$ DECW$SERVER_XKEYBOARD_MAP == "DIGITAL_US_LK401" |
When using XKB, this parameter specifies the number of milliseconds before a keystroke is first repeated. The valid values for this parameter are 0 to 1000. The default is 660.
The following parameter specifies the delay for keystroke repetition:
Example
$ DECW$SERVER_KEY_REPEAT_DELAY == "800" |
DECW$SERVER_KEY_REPEAT_INTERVAL
When using XKB, this parameter specifies the number of milliseconds between repeated keystrokes. The valid values for this parameter are 0 to 1000. The default is 40.
The following parameter specifies the interval for keystroke repetition:
Example
$ DECW$SERVER_KEY_REPEAT_INTERVAL == "20" |
The Security extension (SECURITY), along with the MIT-MAGIC-COOKIE-1 and MIT-KERBEROS-5 protocols, provides additional means for defining which clients are authorized to connect to the X server and what operations they can perform once connected. Use the new parameters in this section to specify the location of the files used with these mechanisms (security policy, X authority, access allowed, and access trusted files).
See Section 3.3.1 for details on defining and implementing an authentication scheme for the DECwindows X11 Display Server. For a brief description of the SECURITY extension, see Section 4.5.1.6.
When using SECURITY, this parameter specifies the name of the security policy file. By default, no file is specified.
The following parameter specifies the security policy file SYS$MANAGER:DECW$SECURITY_POLICY.DAT:
Example
$ DECW$SECURITY_POLICY == "SYS$MANAGER:DECW$SECURITY_POLICY.DAT" |
See Section 3.3.1.5.2 for a description of the security policy file.
This parameter specifies the name of the server X authority file. This file provides records used to authorize client connections to the server. By default, no file is specified. This allows access to the X server from the local SYSTEM account (via DECnet or the Local transport) without requiring additional authentication from the client.
Note that the settings in the X authority file specified by DECW$SERVER_XAUTHORITY apply to server connections made before a user logs into the DECwindows desktop. Once a user logs into the desktop, the user's X authority settings are applied.
If a file is specified, the values from this file are loaded into the server and can be used by all client connections. To allow a normal login process to occur, trusted access must be explicitly granted using the DECW$SERVER_ACCESS_TRUSTED.DAT file.
The following parameter specifies the X authority file SYS$MANAGER:DECW$XAUTH.DAT:
Example
$ DECW$SERVER_XAUTHORITY == "SYS$MANAGER:DECW$XAUTH.DAT" |
See Section 2.6.2.1 for a description of the X authority file.
This parameter specifies the name of the trusted access file. This file lists those clients who maintain trusted access to the server. The default file is SYS$MANAGER:DECW$SERVER_ACCESS_TRUSTED.DAT.
Note that the settings in the trusted access file specified by DECW$SERVER_ACCESS_TRUSTED apply to server connections made before a user logs into the DECwindows desktop. Once a user logs into the desktop, the user's access settings are applied.
The following parameter changes the trusted access file specification:
Example
$ DECW$SERVER_ACCESS_TRUSTED == "SYS$MANAGER:DECW$SERVER1_ACCESS_TRUSTED.DAT" |
This parameter specifies the name of the access allowed file. This file lists those clients who are granted automatic access to the server without requiring additional authentication. The default file is SYS$MANAGER:DECW$SERVER_ACCESS_ALLOWED.DAT.
Note that the settings in the allowed access file specified by DECW$SERVER_ACCESS_ALLOWED apply to server connections made before a user logs into the DECwindows desktop. Once a user logs into the desktop, the user's access settings are applied.
The following parameter changes the allowed access file specification:
Example
$ DECW$SERVER_ACCESS_ALLOWED == "SYS$MANAGER:DECW$SERVER1_ACCESS_ALLOWED.DAT" |
| Previous | Next | Contents | Index |