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

Administering a System: Booting and Shutdown
Abnormal System Shutdowns
Chapter 5546
• The logical volume cannot be used for file system storage, because
the whole logical volume will be used.
To use logical volumes for dump devices (regardless of how many logical
volumes you want to use), include the following dump statement in the
system file:
dump lvol
Configuring No
Dump Devices
To configure a kernel with no dump device, use the following dump
statement in the system file:
dump none
NOTE If you truly want no dump device to be configured into the kernel, you
must use the dump none statement. Omitting dump statements
altogether from the system file causes the kernel to use only the primary
paging device (swap device) as the dump device.
Step 2. When you have edited the system file, build a new kernel file using the
config command (see “Reconfiguring the Kernel (Prior to HP-UX 11i
Version 2)” on page 282 for details on how to do this.)
Step 3. Save the existing kernel file (probably /stand/vmunix) to a safe place
(such as /stand/vmunix.safe) in case the new kernel file cannot be
booted and you need to boot again from the old one.
Step 4. When the time is appropriate, boot your system from the new kernel file
to activate your new dump device definitions.
Run Time Dump Device Definitions As of HP-UX Release 11.0,
unless you are concerned about capturing a dump of your system that
occurs during the earliest stages of the boot process, you now have the
ability to replace or supplement any dump device definitions that are
built into your kernel while the system is booting or running. There are
two ways to do this:
• Using crashconf to read dump entries in the /etc/fstab file (using
crashconf’s -a option)
• Using arguments to the crashconf command, directly specifying the
devices to be configured