Dooglave
asked on
leaving core creation on. umcore and "ulimit -c unlimited" and kernel panic grup.conf edit crashkernel= and chkconfig --level 3 kdump on
Why are, umcore and "ulimit -c unlimited" and kernel panic grup.conf edit "crashkernel=" and "chkconfig --level 3 kdump on:, not set by default
What are the side affects of leaving these enabled indefinitely?
What are the side affects of leaving these enabled indefinitely?
In 64bit environment process size can reach pretty big numbers (many gigabytes). Dumping so much into core can make server unusable for substantial amount of time and can fill up your disk, so limiting core size could be a good precaution.
ASKER
So can a core file be any larger than the amount of physical memory in the system? Does swap usage play a role in increasing the filesize?
Also If understand correctly disk space is about the only drawback to leaving usermode and kernal panic core dump creation turned on. I guess if someone had a history of neglecting or not monitoring their servers we could create a cron job to notify a core dump file was present or even clean up all the old files and just preserve the latest.
Also If understand correctly disk space is about the only drawback to leaving usermode and kernal panic core dump creation turned on. I guess if someone had a history of neglecting or not monitoring their servers we could create a cron job to notify a core dump file was present or even clean up all the old files and just preserve the latest.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.