Kbase P87967: How large should the UNIX maximum core file size be set?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/04/2010 |
|
Status: Verified
GOAL:
How large should the UNIX maximum core file size be set?
GOAL:
What size core file should be allowed on UNIX for Progress processes?
FACT(s) (Environment):
UNIX
Progress/OpenEdge Product Family
FIX:
On UNIX, it's possible that if a Progress process dies abnormally it will create a core file. The core file encompasses the process's memory space plus that of shared memory for all databases that the process is connected to.
This can pose a problem on systems where the combined database shared memory pool is very large because it can easily consume all available file system diskspace.
There is no easy way to determine how large you should set the Operating System maximum core file size setting. As a rule of thumb, 50MB is a good general setting.
Obviously, if a problem occurs and you need to analyze the core file or stacktrace and the core file has been truncated due to O/S settings then you won't be able to.
On some Operating Systems like Sun Solaris and HP-UX, the "ulimit -a" command will show you the current maximum core file size setting.
Please review the Operating System documentation on how to set the value.