Core dump file control
Quoted 4 lines · Michael Sinz
This then causes core dumps to be of the format:
/coredumps/whale.sinz.org-badprogram-13917.core
I had something like this for a long time on my todo list. The idea was to set core_name_format to the name of a named pipe and have an daemon on the other end that logs backtraces to syslogd (something a bit like dr.watson)
Only problem is that it won't handle parallel coredumps very well without some additional (deadlock prone) global locking or alternatively support AF_UNIX stream sockets too that have the concept of multiple streams over a single name.
-Andi
Quoted 7 lines · Andi Kleen
Quoted 4 lines · Michael Sinz
This then causes core dumps to be of the format:
/coredumps/whale.sinz.org-badprogram-13917.core
Quoted 8 lines
I had something like this for a long time on my todo list. The idea was to set
core_name_formatto the name of a named pipe and have an daemon on the other end that logs backtraces to syslogd (something a bit like dr.watson)
Only problem is that it won't handle parallel coredumps very well without some additional (deadlock prone) global locking or alternatively supportAF_UNIXstream sockets too that have the concept of multiple streams over a single name.
Ahh, interesting idea. I have not thought about using pipes since my main concern was needing to put coredumps into a place that can not fill up useful disk and, in the case of the diskless nodes, is writeable since everything else is not. We just grab the core dumps later in order to figure out what went wrong. Under non-development cases we should get close to zero core dumps. (Ahh, if that were only true at this time... :-)
Signature · 3 lines
Michael Sinz ---- Worldgate Communications ---- [email protected] A master's secrets are only as good as the master's ability to explain them to others.