The coreadm Command

This release introduces the coreadm command, which provides flexible core file naming conventions and better core file retention. For example, you can use the coreadm command to configure a system so that all process core files are placed in a single system directory. This means it is easier to track problems by examining the core files in a specific directory whenever a Solaris process or daemon terminates abnormally.

Two new configurable core file paths, per-process and global, can be enabled or disabled independently of each other. When a process terminates abnormally, it produces a core file in the current directory as in previous Solaris releases. But if a global core file path is enabled and set to /corefiles/core, for example, then each process that terminates abnormally would produce two core files: one in the current working directory and one in the /corefiles directory.

By default, the Solaris core paths and core file retention remain the same.

See "Managing Core Files (coreadm)" and coreadm(1M) for more information.