HP-UX System Administrator's Guide: Configuration Management

on the same kcmodule command line, or make the changes in a system file and import
it. (See “Managing Configurations with System Files” (page 192).) Either of these
techniques will ensure that the kernel executable is only relinked once.
Sometimes you may want to force a change to be held for next boot, instead of applying
it immediately. In these cases you can use the -h (hold) option with kcmodule to force
that behavior. HP recommends that this option be used only when the next boot is
expected to be soon. If, for example, the next boot doesn’t happen for months after
making such a change, the system administrator could be unpleasantly surprised at
the effect of a pending change that had been forgotten.
Changes to saved kernel configurations can be made by using the -c (configuration)
option. Such changes are made to the saved configuration immediately, but they won’t
affect the running system until that saved configuration is either loaded or booted. See
“Managing Saved Configurations with kconfig” (page 189) for more information.
When changing module states, kcmodule supports the -b (backup) option to specify
backup behavior, and the -C option to specify a log file comment. See “Recovering
from Errors” (page 197) and “The Kernel Configuration Log File” (page 195) for details.
Managing Kernel Modules with HP SMH
HP SMH can be used to query and change the states of kernel modules in the currently
running configuration. Using HP SMH, you can
• Determine which modules are currently running in the kernel
• View details about a module
• Modify the state of a module
You can view the modules pane by selecting the Modules tab on the HP SMH Kernel
Configuration page, as shown in Figure 10-2.
Managing Kernel Modules with HP SMH 165