Enhanced User Core File Naming

The coreadm(1M) command can be used to uniquely name application core files created by abnormally terminating user processes.

Summary of Change

What’s New for Customers Migrating from HP-UX 11i v1 September 2005?

The coreadm(1M) is a new command introduced in HP-UX 11i v3 to uniquely name application core files created by abnormally terminating user processes.

Legacy behavior in HP-UX is to create a core file under the name “core” for an abnormally terminating processes.

A potential problem with that behavior is that abnormally terminating applications which share the same working directory can overwrite each other’s core files. By uniquely naming core file names, application core files will not be overwritten.

The coreadm(1M) command offers the following features:

Core file names can be differentiated by
- Machine name (as stated by uname)
- PID
- Time stamp
- Node name
- Executable file
- UID/GID
- Processor ID of the running thread when core was generated
- Directory where the core file is placed
System wide and per-process level control to enable or disable core file creation.
The default is legacy behavior. (File name is “core.”)

What’s New for Customers Migrating from HP-UX 11i v2 June 2006?

See “What’s New for Customers Migrating from HP-UX 11i v1 September 2005?”

Impact

By default, this feature will not be turned on. System-wide core file naming can only be set by the super-user. Normal users can override core file settings for processes that they own.

Compatibility

The default is still the legacy behavior which creates the core file under the name “core.”

Performance

Core file creation is not a performance-sensitive code path; therefore, this feature shouldn’t affect performance.

Documentation

For further information, see the coreadm(1M) and coreadm(2) manpages.

Obsolescence

Not applicable.