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

configuring an X Server on HP-UX Module section The Module section specifies which X Server modules should be loaded. The types of modules normally loaded in this section are X Server extension modules, and font rasterizer modules. Most other module types are loaded automatically when they are needed via other mechanisms. There may only be one Module section in the configuration file. The format of the Module section is as follows: Section "Module" Load "ModuleName" . . . [SubSection "ModuleName" Option EndSubSection] . . . EndSection Load instructs the server to load the module called ModuleName. The module name given should be the module's extension name, not the module file name. The extension name is case sensitive, and does not include the "lib" prefix, or the library suffix (for example, "so.1"). Example: the Double Buffered Extension (DBE) can be loaded with the following entry: Load "dbe" Beginning with the December 2002 patch, the "Load" directive is no longer needed to load extensions because the brokering mechanism ensures that the correct extensions are loaded automatically. SubSection also instructs the server to load the module called ModuleName. The module name given should be the module's extension name, not the module file name. The extension name is case sensitive, and does not include the "lib" prefix, or the library suffix (for example, "so.1"). The difference is that the listed Options are passed to the module when it is loaded. Modules are searched for in each directory specified in the ModulePath search path and in the drivers, input, extensions, fonts, and HP-UX subdirectories of each directory in the ModulePath. If ModulePath is not specified in the Files section, the default ModulePath is searched. Noload instructs the server to not load the module called ModuleName. 4-8 Graphics Administration Guide