Date: Sun, 21 Jan 2007 15:04:21 +0100
From: Johannes Stezenbach <js@linuxtv.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Theodore Tso <tytso@mit.edu>, Joe Barr <joe@pjprimer.com>,
       Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Message-ID: <20070121140421.GA13425@linuxtv.org>
References: <1169242654.20402.154.camel@warthawg-desktop> <20070120173644.GY24090@1wt.eu> <20070121055456.GC27422@thunk.org> <20070121070557.GB31780@1wt.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070121070557.GB31780@1wt.eu>
User-Agent: Mutt/1.5.13 (2006-08-11)
Subject: Re: Serial port blues
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1238
Lines: 28

On Sun, Jan 21, 2007 at 08:05:57AM +0100, Willy Tarreau wrote:
> On Sun, Jan 21, 2007 at 12:54:56AM -0500, Theodore Tso wrote:
> > On Sat, Jan 20, 2007 at 06:36:44PM +0100, Willy Tarreau wrote:
> > 
> > > Now he must be careful about avoiding busy loops in the rest of the
> > > program, or he will have to use the reset button.
> > 
> > An easy way of dealing with this is to have an sshd running
> > an alternative port running at a nice high priority (say, prio 95 or
> > so).  That way, if you screw up, you can always login remotely and
> > kill the offending program.
> >
> > There is also a RT Watchdog program which can be found on
> > rt.wiki.kernel.org which can be used to recover from runaway real-time
> > processes without needing to hit the reset button.
> 
> Thanks for those hints, I've been used to play with the reset button,
> at least it has forced me to double check my code before running it :-)

I think SysRq-N sets all processes with RT-priority to non-RT.


Johannes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/