On Sat, Nov 18, 2006 at 03:04:13AM +0100, Folkert van Heusden wrote: > > > > I found that sometimes processes disappear on some heavily used system > > > > of mine without any logging. So I've written a patch against 2.6.18.2 > > > > which emits logging when a process emits a fatal signal. > > > Why not to patch default signal handlers in glibc, to have not only > > > stderr, but syslog, or /dev/kmsg copy of fatal messages? > > Afaik when a proces gets shot because of a segfault, also the libraries > > it used are shot so to say. iirc some of the more fatal signals are > > handled directly by the kernel.
Kernel sends signals, no doubt. Then, who you think prints that "Killed" or "Segmentation fault" messages in *stderr*? [Hint: libc's default signal handler (man 2 signal).] > Also: what about statically build programs? "-lc" embeds libc in static binary, no? IMHO it's not a lkml issue. Here are many who would say you, that userspace preblems are userspace problems. ____ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
