Dear subscribers

I have a peculiar problem. On one of my customer’s servers we would
like to configure the "init core file pattern" to avoid that core
dumps overwrite each other. The problem is that while it works just
fine on our development servers it does not work at our customers
servers. Event though coreadm reports:

# coreadm
global core file pattern:
init core file pattern: core.%f.%p
global core dumps: disabled
per-process core dumps: enabled
global setid core dumps: disabled
per-process setid core dumps: disabled
global core dump logging: disabled

there is no filename and no process id attached to the file name, i.e.
the name of a core dump is just "core". Could it possibly be that the
server requires a reboot for "init core file pattern" to apply? This
is not something that we want to do casually so we haven’t tried it
yet. BTW, it was not needed on our development servers.

Any help on this matter would be most appreciated.

Regards, Ola

On Jun 1, 9:24 am, ola.thean...@otsystem.com wrote:
[..]
>
> there is no filename and no process id attached to the file name, i.e.
> the name of a core dump is just "core". Could it possibly be that the
> server requires a reboot for "init core file pattern" to apply? This
> is not something that we want to do casually so we haven’t tried it
> yet. BTW, it was not needed on our development servers.
>
> Any help on this matter would be most appreciated.
>
> Regards, Ola

From, man coreadm, the -g option may not be useless...

-g pattern
Set the global core file name pattern to pattern. The pattern must
start with a / and can contain any of the special % variables
described in the DESCRIPTION.

%p
process-ID

%u
effective user-ID

%g
effective group-ID

%f
executable file name, up to a maximum of MAXCOMLEN characters

%n
system node name (uname -n)

%m
machine name (uname -m)

%t
decimal value of time(2)

%%
literal %

You may use a timestamp.....
You may update the config file, and then, use the -u option(changes
take effect)...


Kartik Vashishta

On Jun 1, 9:24 am, ola.thean...@otsystem.com wrote:
[..]
>
> there is no filename and no process id attached to the file name, i.e.
> the name of a core dump is just "core". Could it possibly be that the
> server requires a reboot for "init core file pattern" to apply? This
> is not something that we want to do casually so we haven’t tried it
> yet. BTW, it was not needed on our development servers.
>
> Any help on this matter would be most appreciated.
>
> Regards, Ola

Maybe, post the file, /etc/coreadm.conf

You might be able to test using the gcore command, the -g option
perhaps uses configurations based on coreadm...see man gcore

Kartik Vashishta

On Jun 1, 7:05 pm, p...@kartik.com wrote:
> On Jun 1, 9:24 am, ola.thean...@otsystem.com wrote:
>>
>>
>>
> Maybe, post the file, /etc/coreadm.conf
>
> You might be able to test using the gcore command, the -g option
> perhaps uses configurations based on coreadm...see man gcore
>
> Kartik Vashishta

less /etc/coreadm.conf
#
# coreadm.conf
#
# Parameters for system core file configuration.
# Do NOT edit this file by hand -- use coreadm(1) instead.
#
COREADM_GLOB_PATTERN=
COREADM_INIT_PATTERN=core.%f.%p
COREADM_GLOB_ENABLED=no
COREADM_PROC_ENABLED=yes
COREADM_GLOB_SETID_ENABLED=no
COREADM_PROC_SETID_ENABLED=no
COREADM_GLOB_LOG_ENABLED=no

Regards, Ola