Hi Team,

Yes, I just observed that creating the /etc/coreadm.conf modifying the other coreadm settings.

I have given the commands to set it back to its previous state below ( I have compared before and after output and update the commands where ever it requires the modification:

AFTER:
global core file pattern: /var/cores/core.%z.%f.%u.% ======⇒ to change #coreadm -e global -g /var/share/cores/core_%n_%f_%u_%g_%t_%p
global core file content: default
kernel zone core file pattern:
init core file pattern: core
init core file content: default
global core dumps: disabled =============> to enable #coreadm -e kzone -g ""
kernel zone core dumps: disabled
per-process core dumps: enabled =======> to disable #coreadm -e process -g ""
global setid core dumps: disabled ======> to enable #coreadm -e global-setid -g ""
per-process setid core dumps: disabled
global core dump logging: disabled =====>to enable #coreadm -e log -g ""
diagnostic core dumps: enabled
retention policy: summary
core diagnostic alert: disabled ======>> to enable #coreadm -e alert -g ""
automated service request: disabled =====>> to enable #coreadm -e asr -g ""

Regards

Jay

Hi Team,

Apart from creating /etc/coreadm.conf, I couldn't find any direct command to null the kernel zone core file pattern, command line strictly tells that the path should start with /,so I don't think its possible to set it directly.

Regards

Jay