Messages in this thread | | | Date | Fri, 16 Jul 1999 14:31:53 +1000 | From | Richard Gooch <> | Subject | Re: kernel thread support - LWP's |
| |
Jamie Lokier writes: > Richard Gooch wrote: > > I once wanted to selectively stop some threads > > in nfsd on Solaris, and I couldn't do that easily. I had to root > > around in /proc to target the individual threads. Yuk. What I wanted > > to do was: > > # kill -STOP pid > > The downside to this is that threads must defensively assume you > _might_ kill individual ones. Presumably in the Solaris model, they > can be written to be codependent? I'm thinking of things like > mutexes and so on.
In this case, I didn't want the application to know what I was up to. I *wanted* to violate it, without it being able to work around me.
> You could always bring up the debugger to mess with an individual > thread. You'd have to do that for anything that's not a > system-defined thread but a user-defined one anyway.
The debugger isn't always appropriate. Especially not if you're trying to do something in an automated script (which I was). This is why I think it's better overall to expose threads.
Regards,
Richard....
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |