[Top] [Prev] [Next] [Contents] [Index]

Configuring X Server Module Loading

Most of the local clients, extensions, libraries, and protocols included in NCDware exist as X server modules.

All modules are listed in the online file modsmodel.doc (model is the model on which the modules run, such as modshmx.doc for the HMX family of terminals). This file is installed in the modules directory, which is described in "Changing the X Server Module Location". The modules are also listed in the Release Notes.

The Change Quick Setup, Console, Lock Screen, and Logout local clients are not loadable modules. They are always available unless disabled.

Changing X Server Module Load Policy

By default, the terminal loads X server modules when a user or client needs them and unloads them when the user logs out or when the server needs memory. This load method is called on-demand.

X server modules can also be loaded at boot time. At-boot loading is useful for clients that take a long time to load, such as the local Motif Window Manager. The LAT server module must be loaded at boot to be available for use.

You can also disable server modules so that they cannot be loaded. Disabled local clients appear in a dithered (grayed-out) font in the Console menus.

To change X server module load policy, list the modules you want to change and the desired load policies in the modules-load-policy remote configuration parameter (not saved in NVRAM). The parameter is a table with entries in the format name policy where:

name is the name of the module, as listed in the modsmodel.doc file.
policy is the load policy: "on-demand," "at-boot," or "disable."

For example, the following table sets the local Motif Window Manager module to load at boot and disables the Change Setup Parameters menu, touch screen module, and PEX module:

modules-load-policy = {
         {mwm at-boot}
         {touchscreen disable}
         {pex disable}
         {setup disable}

(Setup -> Change Setup Parameters -> Loadable Modules -> Load Policy).

Changing the X Server Module Location

If you install NCDware using ncdinstall, X server modules are placed in the /tftpboot/ncd/release/modsmodel directory, where:

release is the release version number, such as Xncd.5.0.xxx.
model is the terminal model, such as modshmx for modules for the HMX series of terminals.

On systems running secure TFTP, ncdinstall places the server modules in the /secure-dir/tftpboot/ncd/release/modsmodel directory.

When the terminal boots, it looks first for server modules in the directory specified in the modules-directory parameter (not saved in NVRAM). The X server sets the value of modules-directory based on the location of the X server boot image. If the modules are not there, the terminal looks in /tftpboot/ncd/release/modsmodel.

If a terminal cannot find X server modules, error messages result. To find out where the X server is looking for modules and correct the location, you can use the Change Quick Setup local client to display and change the current value of Files -> Loadable Modules Directory (or Change Setup Parameters -> Loadable Modules -> Loadable Modules Directory).

If you change the location of the server modules on the host, you must change the value of the modules-directory parameter to the new location. For example:

modules-directory = /usr/vendor/ncd/modshmx

Changes are automatically recorded in the file service table.

[Top] [Prev] [Next] [Contents] [Index]

Send comments, suggestions, or questions about this document to the NCD Technical Publications Department by Internet e-mail. Write to us at techpubs@ncd.com.
Copyright © 1997, NCD Inc. All rights reserved.