Manualshelf

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

ManualsBrandsHP ManualsSoftwareHP-UX 11i v1.6 Technical Computing (TCOE) LTU
351352353354355356357358359360
Configuring a System
Reconfiguring the Kernel (HP-UX 11i Version 2)
Chapter 3352
usage tables (including top consumers) for supported kernel tunables.
These data also enable usage graphs in the kcweb tool. Monitoring is
turned on by default when the kcweb tool is installed.
For more information, see the kcalarm (1M), kcmond (1M), and kcusage
(1M) manpages.
Managing the Running Configuration using kconfig
The kconfig command has two options that are useful for dealing with
changes to the currently running kernel configuration that are being
held for next boot. Configuration changes are held for next boot when
requested (using the -h (hold) option of kcmodule or kctune, or the -n
(next boot) option of kconfig). Configuration changes are also held for
next boot when they cannot be applied to the currently running system.
To get a list of changes being held for next boot, run kconfig -D
(Differences). This is really just a short cut for running kcmodule -D and
kctune -D. Similarly, to get a list of configuration settings that are set to
nondefault values, run kconfig -S (Set). This is a short cut for running
kcmodule -S and kctune -S.
1
If you decide that you don’t want those changes to be applied at next boot
after all, run kconfig -H (unHold). All changes being held for next boot
will be discarded.
For more information on changes being held for next boot, see
“Persistence of Changes” on page 324.
Managing Saved Configurations with kconfig
When you have an HP-UX kernel configuration that satisfies your needs,
you may want to save a copy of it to protect yourself against inadvertent
configuration changes. Or, you may want to have multiple kernel
configurations, so that you can switch between them easily. HP-UX
allows you to save as many kernel configurations as you wish (subject to
available disk space in /stand), and to modify them and use them at
will.
1. Device binding changes are not included in these outputs. See
“Managing Device Bindings” on page 359.