Two new configurable core file paths that can be enabled or disabled independently of each other are:
A per-process core file path, which defaults to core and is enabled by default. If enabled, the per-process core file path causes a core file to be produced when the process terminates abnormally. The per-process path is inherited by a new process from its parent process.
When generated, a per-process core file is owned by the owner of the process with read/write permissions for the owner. Only the owning user can view this file.
A global core file path is disabled by default. If enabled, an additional core file with the same content as the per-process core file is produced by using the global core file path.
When generated, a global core file is owned by the superuser with read/write permissions for the superuser only. Non-privileged users cannot view this file.
When a process terminates abnormally, it produces a core file in the current directory as in previous Solaris releases. But if the global core file path is enabled and set to /corefiles/core, for example, then each process that expires produces 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:
A setuid process does not produce core files using either the global or per-process path.
The global core file path is disabled.
The per-process core file path is enabled.
The per-process core file path is set to core.