Configuring Core Files
core files are created when a program or an application terminates abnormally. The default location for a core file to be written is the current working directory. However, as the system administrator, you might want to configure the system so that all core files are written to a central location. This would make administration and management of core files much easier because core files can sometimes take up a significant amount of disk space.
What is a core file?
A core file is a point-in-time copy (snapshot) of the RAM allocated to a process. The copy is written to a more permanent medium, such as a hard disk. A core file is useful in analysing why a particular program crashed.
A core file is also a disk copy of the address space of a process, at a certain point in time. This information identifies items, such as the task name, task owner, priority, and instruction queue in execution at the time the core file was created.
Managing core files
You manage core files by using the
coreadm [-g pattern] [-G content] [-i pattern] [-I content] [-d option...] [-e option...] coreadm [-p pattern] [-P content] [pid] coreadm -u
The following table lists the options available for the
|Sets the global core file name pattern.
|Sets the global core file content using one of the description tokens.
|Sets the per-process core file name pattern.
|Sets the per-process core file name to content.
|Disables the specified core file option.
|Enables the specified core file option.
|Sets the per-process core file name pattern for each of the specified pids.
|Sets the per-process core file content to content.
|Updates the systemwide core file options from the configuration file /etc/coreadm.conf.
coreadm with no options displays the current configuration, which you can determine by reading the file
A core file name pattern consists of a file system pathname, along with embedded variables. These variables are specified with a leading % character. The values are then expanded when a core file is created. The following table lists valid pattern variables.
|Specifies the process ID (PID).
|Specifies the effective user ID.
|Specifies the effective group ID.
|Specifies the executable file directory name.
|Specifies the executable filename.
|Specifies the system node name. This is the same as running uname -n.
|Specifies the machine name. This is the same as running uname -m.
|Specifies the decimal value of time, as the number of seconds since 00:00:00 January 1, 1970.
|Specifies the name of the zone in which the process is executed (zonename).
|Specifies the a literal % character.
-e flags of the
coreadm command can take several options.
|Allows core dumps, using the global core pattern.
|Allows core dumps, using the per-process core pattern.
|Allows set-id core dumps, using the global core pattern.
|Allows set-id core dumps, using the per-process core pattern.
|Produces a syslog message when an attempt is made to generate a global core file.
To modify the core file configuration so that all files are dumped into the directory
/cores and named
core, followed by the system name and then the name of the program being run, we would execute:
root, use the
coreadmcommand to display the current coreadm configuration:
# coreadm global core file pattern: global core file content: default init core file pattern: core init core file content: default global core dumps: disabled per-process core dumps: enabled global setid core dumps: disabled per-process setid core dumps: disabled global core dump logging: disabled
- As root, issue the following command to change the core file setup:
# coreadm -i /cores/core.%n.%f
coreadmagain to verify that the change has been made permanent:
# coreadm global core file pattern: global core file content: default init core file pattern: /cores/core.%n.%f init core file content: default global core dumps: disabled per-process core dumps: enabled global setid core dumps: disabled per-process setid core dumps: disabled global core dump logging: disabled