Table of Contents
Advertisement
switch on the panel. Otherwise, you can turn the system o and then back on
to initiate the boot sequence.
You will probably notice a few di erences in boot behavior as compared with
your normal boot sequence. Your system might save a \core" le to disk. This
core le is a \snapshot" of the previously running kernel at the time that it
panicked. If necessary, this core le can be analyzed using special tools to
determine more about what caused the panic.
For HP-UX, core les are quite large and, if your system is so
Note
con gured, they are saved to the directory
HP-UX 9, or
need to save these les for future analysis (something that
isn't usually required), it is best to save them to tape and
remove them from your le system in order to free up space.
If you
core les. Core les are used in rare circumstances to diagnose
hard-to- nd causes of system panics.
If the reason your system panicked was because of a corrupted le system,
will report the errors and any corrections it makes. If the problems were
fsck
associated with your root le system,
when it's nished. When you do this on an HP-UX system, use the following
command:
reboot -n
The
option tells
-n
reboot
has made all the corrections on disk, you do not want to undo the
fsck
changes by writing over them with the corrupt memory bu ers.
/var/adm/crash
know why your system panicked, you can delete the
will ask you to reboot your system
fsck
not to sync the le system before rebooting. Since
/tmp/syscore
on HP-UX 10. If you feel you
Dealing With Problems
on
9
9-11
Advertisement
Table of Contents
