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

HP-UX Handbook – Rev 13.00 Page 30 (of 33)
Chapter 07 Kernel Configuration
October 29, 2013
For example:
# kcmodule -P ALL autofs cachefs
name autofs
desc Automounter File System
version 1.0
timestamp Tue Sep 12 21:53:28 2006 [45078EC8]
state static
cause best
next_state static
next_cause best
capable static unused
depend module nfswrp:0.0.0
depend interface HPUX_11_31_PERF:1.0
Each kernel module in the currently running configuration has a state, which describes how the
module is being used. The possible states are:
unused The module is installed on the system but not in use.
static The module is statically bound into the kernel executable. This is the most
common state. Moving a module into or out of this state requires relinking
the kernel executable and rebooting.
loaded The module is dynamically loaded into the kernel. Newer modules support
this state. Such modules may be added to the kernel configuration or
removed from it without rebooting.
auto The module will be dynamically loaded into the kernel when it is first
needed, but it hasn’t been needed yet.
When kcmodule is giving information about the currently running system, and there are
configuration changes being held for next boot, kcmodule will list both the current state and the
state at next boot. For next boot, the same states are used, with complementary meanings:
unused The module will not be used.
static The module will be statically bound into the kernel executable.
loaded The module will be dynamically loaded into the kernel during the boot
process..
auto The module will be dynamically loaded into the kernel when it is first
needed after each boot