Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a System
Reconfiguring the Kernel (HP-UX 11i Version 2)
Chapter 3 355
Using and Modifying Saved Configurations
Creating Saved Configurations Saved kernel configurations can be
created in three ways: by saving the currently running configuration, by
copying an existing saved configuration, or by reading a system file.
To save the currently running configuration, use kconfig -s (save). The
resulting saved configuration will include any changes to the currently
running configuration that are being held for next boot.
An existing saved configuration can be copied using kconfig -c (copy).
For information on working with system files, see “Managing
Configurations with System Files” on page 356.
Using Saved Configurations A saved configuration can be loaded
using kconfig -l (load). This changes the configuration of the currently
running kernel to match what was saved. If the configuration can be
changed without a reboot, the changes will take effect immediately.
Otherwise, all of the changes will be held for next boot.
Sometimes you may want to force the configuration change to be held for
next boot, instead of applying it immediately. In these cases, you can
mark the saved configuration for use at next boot using kconfig -n
(next boot). 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 you make such a change, the system administrator
could be unpleasantly surprised at the effect of a pending change that
had been forgotten.
To find out which saved configuration is marked for use at next boot, use
kconfig -w (which). This command also identifies the saved
configuration that was most recently loaded or booted, or the system file
that was most recently imported.
Modifying Saved Configurations To modify the module state
settings and tunable value settings in a saved configuration, use the -c
(configuration) option of the kcmodule and kctune commands,
respectively. Saved configurations can also be changed by changing their
system file and then importing it; see “Managing Configurations with
System Files” on page 356.