Prev: disable screen lock in S10
Next: Require Service password for 6800 so I can run setchs
From: Amitava on 26 Apr 2010 14:42
Here's my coreadm output:

global core file pattern: /var/core/core.%f.%p.%n.%u.%g.%t
init core file pattern: /var/core/core.%f.%p.%n.%u.%g.%t
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps: enabled
per-process setid core dumps: enabled
global core dump logging: enabled

Most of the time, the core files (global and init) are in /var/core,
but sometimes, there's a file simply named "core" in the working
directory.

This is on Solaris 9 9/05 running on Sun-Fire-880.

What could be the reason for this?

Thanks.
From: Roland Titze on 27 Apr 2010 02:47
On 26 Apr., 20:42, Amitava <ad_...(a)yahoo.com> wrote:
> Here's my coreadm output:
>
>      global core file pattern: /var/core/core.%f.%p.%n.%u.%g.%t
>        init core file pattern: /var/core/core.%f.%p.%n.%u.%g.%t
>             global core dumps: enabled
>        per-process core dumps: enabled
>       global setid core dumps: enabled
>  per-process setid core dumps: enabled
>      global core dump logging: enabled
>
> Most of the time, the core files (global and init) are in /var/core,
> but sometimes, there's a file simply named "core" in the working
> directory.
>
> This is on Solaris 9 9/05 running on Sun-Fire-880.
>
> What could be the reason for this?
>
> Thanks.

Hi Amitava,

maybe you forgot to call "coreadm -u"?

BR
--
Roland
 | 
Pages: 1
Prev: disable screen lock in S10
Next: Require Service password for 6800 so I can run setchs