Quote:
Originally Posted by
b1f30
I found a huge vmcore file that was 600+MB. None of my lab people needed it.....
This is a reason that many people simply set the file size of core files and dumps to zero (or simply disable completely), as they don't debug them (since they are not application or kernel developers).
If you don't use them and do not actively look for or manage them, they can really cause problems, as you experienced.
So, if you are not using them (or do not know how to use them), just disable them.....
You can always turn them back on if you start to see problems where you might need a core file, etc
Edit: See also:
http://developers.sun.com/solaris/ar...core_dump.html
See for example, this example, in the link above:
Below is a typical scenario, which shows the current system configuration for core dumps:
Quote:
-bash-3.00# coreadm
global core file pattern:
global core file content: default
init core file pattern: core
init core file content: default
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