From: Nick 'S. M. <sh...@zo...> - 2002-02-21 22:35:57
|
On Thu, Feb 21, 2002 at 09:58:37AM -0500, Jeff Dike wrote: > sh...@zo... said: > > If I'm doing this a totally bone-headed way, I'm sure you'll let me > > know ... hey, I said it was trivial! > > The tracing thread shouldn't call into the kernel like that. Actual kernel > threads are the only things that should be running kernel code. Oh, fair enough. I was hoping the eventual behavior (finding pid 1 and SIGINTing it) would sort itself out. I guess a better way would be for the tracing thread to catch SIGHUP, and to SIGHUP a kernel thread, which would then SIGINT the init thread. Maybe? > What's the matter with the mconsole 'cad' command (aside from the fact that > I think it's not documented anywhere :-)? Ah, well, mainly that I didn't know it existed. I'd still like to be able to do it with a signal, just so I can script horrible things like: ps auxww | grep 'tracing\ thread' | awk '{print $2;}' | xargs kill -HUP Hopefully something useful should come out of all this mucking around: I'm setting up IPv6 virtual networks & trying to do simulation and conformance testing using UML. There's probably a paper in it :-) -----sharks |