On Tue, Aug 30, 2005 at 10:01:21AM +0200, Sven Ladegast wrote:> [..] combined > with an automatic oops/panic/bug-report this would be _very_ useful I think.

That would be nice addition IMHO. It'll be more complex since it'llinvolve netconsole dumping and passing the klive session to the kernelsomehow (userland would be too unreliable to push the oops to theserver). The worst part is that oops dumping might expose random kerneldata (it could contain ssh keys as well), so I would either need topurify the stack/code/register lines making the oops quite useless, ornot to show it at all (and only to show the count of the oopsespublically). A parameter could be used to tell the kernel if the wholeoops should be sent to the klive server or if only the notification anoops should be sent (without sending the payload with potentiallysensitive data inside).-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to majordomo@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.htmlPlease read the FAQ at http://www.tux.org/lkml/