Core files...

[Oleg Goudovany_1]

Hi, All!

Perhaps somebody know "beautiful way" for and termination core files?

Thanx in advance.
Oleg

[Oleg Goudovany_1]

SORRY!

Between "for" and "and"must be "observation of occurrence".

Oleg

[David Navarro]

Hi, create a directory named core. And core files will not be created.

[David Navarro]

Sorry, this directory must be created in the same place where core files appears.
This do not solves the cause of core, but left your disk clean.

I hope it help you !

[Stefan Farrelly]

WE have symbolic links in the directories they most ocurr in pointing to /dev/null - this way no corefiles left around hogging disk space.

eg.
/home//*
/tmp
/
and application directories.

eg. ln -s /dev/null /tmp/core

[Santosh Nair_1]

If you're using the POSIX shell, i.e. /bin/sh as your default shell, you can also use ulimit to change the max size of the core file to 0 blocks, i.e. no core:

in .profile add:

ulimit -c 0

-Santosh

[Bill McNAMARA_1]

patch your app!

# file core

figure out what it went down on and what core'd

get the Wildebeest debugger
from hp.com/go/languages

# gdb /path/to/cored/application /path/to/corefile/core

to look at the stack.

Search on the itrc for some of the signal/stack strings and apply the patch.

remove the core and never get the same one again!!!

or ln -s as above (good for webservers and less maintained directories)

Later,
Bill