To Configure Solaris OS to Generate Core Files

This procedure shows you how to use the coreadm command to configure the system so that all process core files are placed in a single system directory. This means it is easier to track problems by examining core files in a specific directory whenever a Solaris OS process or daemon terminates abnormally.

Before You Begin

Make sure that the /var file system where the core files are generated has sufficient space. Once you configure Solaris OS to generate core files as shown here, all processes that crash write a core file to the /var/cores directory.

1. Run the following commands as root.

   mkdir -p /var/cores
   coreadm -g /var/cores/%f.%n.%p.%t.core -e global -e global-setid -e log -d process -d proc-setid

   In this command:

   -g

   Specifies the global core file name pattern. Unless a per-process pattern or setting overrides it, core files are stored in the specified directory with a name such as program.node.pid.time.core, for example: mytest.myhost.1234.1102010309.core.

   -e

   Specifies options to enable. The preceding command enables:

   • Use of the global (that is, system-wide) core file name pattern (and thereby location)

   • Capability of setuid programs to also dump core as per the same pattern

   • Generation of a syslog message by any attempt to dump core (successful or not)

   -d

   Specifies options to disable. The preceding command disables:

   • Core dumps per the per-process core file pattern

   • Per-process core dumps of setuid programs

   The preceding command stores all core dumps in a central location with names identifying what process dumped core and when. These changes only impact processes started after you run the coreadm command. Use the coreadm -u command after the preceding command to apply the settings to all existing processes.

2. Display the core configuration.

   # coreadmglobal core file pattern: /var/cores/%f.%n.%p.%t.core init core file pattern: core global core dumps: enabled per-process core dumps: disabled global setid core dumps: enabled per-process setid core dumps: disabled global core dump logging: enabled

   See the coreadm man page for further information.

3. Set the file size as large as possible, using the ulimit command.

   # ulimit -c unlimited # ulimit -a coredump(blocks) unlimited

   See the ulimit(1) man page for details.

4. Verify that applications can in fact generate core files.

   # cd /var/cores # sleep 100000 & [1] pid # kill -8 pid # ls

   You should see a core file for the sleep process you killed.