HP-UX HB v13.00 Ch-07 - Kernel Configuration

HP-UX Handbook – Rev 13.00 Page 31 (of 33)
Chapter 07 Kernel Configuration
October 29, 2013
When kcmodule is giving information about a saved configuration, the same states are used.
Next to each module state is a Cause that tells why the module is (or will be) in that state. The
causes are:
explicit The system administrator explicitly chose the state.
best The system administrator chose to use the module, but didn’t choose a
specific state, so the module is in its best state as determined by the
module developer.
auto The module was in auto state, and was automatically loaded when
something tried to use it.
required The module was marked required by its developer.
depend The module is in use because some other module in the configuration
depends on it.
Different modules can support different states. Nearly all modules can be in static state, but only
a few support loaded or auto states. Many modules can be in unused state, but required modules
cannot. The Capable line in the output shows which states a module supports.
Modules often have dependencies between them. For example, device drivers typically cannot be
configured into the kernel unless the driver support modules are also configured. Dependencies
like this are shown on the Depends On lines in the output. A module can be dependent on a
particular other module, specified by name and version. A module can also be dependent on an
interface that must be supplied by some other module, without saying specifically which
modules supply that interface. Modules that supply such interfaces have an Exports line in the
output, listing the interfaces they export.
Interpreting Tunable Information
Looking at the sample output below, for example:
# kctune -P ALL nproc
name nproc
module pm_proc
desc Maximum number of processes on the system
defvalue 4200
bootvalue 4200
current 4200
next_boot 4200
expr Default
next_expr Default
min 100
max 131072
dynamic y