Information Technology Reference
In-Depth Information
A copy of any core file produced by any
setuid
program is placed in the
/var/core
directory. If a privileged user has enabled the per-process
setuid
configuration by using the following command:
# coreadm -e proc-setid
the users can then set core file generation on a per-process basis for any pro-
gram (
setuid
or non-
setuid
) using the previously described per-process
configuration procedure.
Core File Logging
The
coreadm
command can also be used to enable logging of core file gen-
eration using the system logging (
syslog
) facility. The following command
can be used to enable logging:
# coreadm -e log
Disabling Core File Configurations
The
global
,
process
,
global-setid
,
proc-setid
, or
log
configurations can
also be disabled as required. For example, the following command can be
used to disable the per-process configuration:
# coreadm -d process
Displaying the Current Core File Configuration
To determine whether and where core files are being generated, use the
coreadm
without any arguments to display the current core file configuration:
# coreadm
global core file pattern: /var/core/core.%f.%p
init core file pattern: core
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps: disabled
per-process setid core dumps: disabled
global core dump logging: disabled
Crash Dump Management
Software problems in the operating system (and any loaded device drivers) or
hardware malfunctions can cause the operating system to stop running, or
crash
. The memory image (executable program and data) of the operating
system when this fault occurs can be saved or
dumped
to disk. This
crash dump
can be thought of as a core dump of the operating system.
