Re: killing a set of user processes causes system

On Thu, Dec 14, 2006 at 02:14:28PM -0500, John David Anglin wrote:
> > Yes. We talked about this before. You have to set up a serial console
> > to your C3K, and issue a SYSRQ-T to show where the process is stuck in
> > the kernel.
> 
> I know but that's a problem.  Can't capture enough info to graphics
> console.  Don't have the right cable for a serial console, so I would
> probably have to build it.  The machine's downtown and I haven't been
> driving for the last two weeks.  Before that, Luxcom was sucking up
> most of my time.

I have a bunch of null-modem cables; you can borrow one if you like.
Heck, if you give me directions (and sort out access permissions),
I can go and install it for you.

> I've now using ethernet consoles for the servers but that's not an
> option for the c3k.  Really, it would be great if it were possible
> to do a SYSRQ-T over a standard ssh link.

Ah, /proc/sysrq-trigger is your friend here.

Best of luck with your eye problems!