where will the core dump be saved?

The core dump configuration in your non global zone is

A user is running a process in a non-global zone (testzone) and the process crashes. The process
information is:
user126632618017:46:42pts/20:00/usr/bin/bash
When the user’s process crashes in testzone, a non-global zone, where will the core dump be
saved?

The core dump configuration in your non global zone is

A user is running a process in a non-global zone (testzone) and the process crashes. The process
information is:
user126632618017:46:42pts/20:00/usr/bin/bash
When the user’s process crashes in testzone, a non-global zone, where will the core dump be
saved?

A.
The file will be stored in the non-global zone’s directory: /var/core/pprocess/core.hash.2663.

B.
The file will be saved in the global zone’s directory: /var/core/core.bash.2663.

C.
A core file cannot be generated in a non-global zone because it shares the kernel with the
global zone.

D.
The file will be stored in the global zone’s directory: /var/core/pprocess/core.bash.2663.

E.
The file will be saved in non-global zone’s directory: /var/core/core.bash.2663

Explanation:
The line
init core file pattern: /var/core/core.%f.%p
will be used for the non-global process to determine the destination of the dump file.

Note: When a process is dumping core, up to three core files can be produced: one in the perprocess location, one in the system-wide global location, and, if the process was running in a local
(non-global) zone, one in the global location for the zone in which that process was running.
Reference: man coreadm

Show Hint

Leave a Reply 6

Your email address will not be published. Required fields are marked *

Ilya

Ilya

root 17392 17390 0 14:08:15 ? 0:00 /usr/lib/autofs/automountd
root@testzone:~# kill -6 17392
root@testzone:~# ls /var/core/pprocess
core.automountd.17392
root@testzone:~# ls /var/core/
core.automountd.17392 pprocess
root@testzone:~# coreadm
global core file pattern: /var/core/core.%f.%p
global core file content: default
init core file pattern: /var/core/pprocess/core.%f.%p
init core file content: default
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps: disabled
per-process setid core dumps: disabled
global core dump logging: disabled

this means A or E? )

Reply

g

g

I would put my vote on “E” instead of “A”, because “A” says, that the core dump, will be savedin the non-global zone.

God bless!

Reply

HARI

HARI

Should be A

http://www.oracle.com/technetwork/server-storage/solaris/manage-core-dump-138834.html

The Solaris OS attempts to create up to three core dump files for each abnormally terminated process. One of the core dump files, which is called the per-process core file, is located in the current directory. Another core dump file, which is called the global core file, is created in the system-wide location. If the process is running in a local zone, a third core file is created in the global zone’s location.

The per-process core dumps: enabled line indicates a per-process core dump will be generated for each abnormal process.

The init core file pattern line indicates the contents will be gathered from the live process to the per-process core dump.

Reply