Date: Mon, 25 Aug 2008 14:20:24 +0200
From: Willy Tarreau <w@1wt.eu>
To: Chris Frey <cdfrey@foursquare.net>
Cc: Joe Peterson <joe@skyrush.com>, Vegard Nossum <vegard.nossum@gmail.com>,
       linux-kernel@vger.kernel.org
Subject: Re: Visible Ctrl-C in latest kernels
Message-ID: <20080825122024.GA19337@1wt.eu>
References: <20080822201537.GA18242@foursquare.net> <19f34abd0808230253w663722dcwde1303998e194ddf@mail.gmail.com> <48B04E42.3030405@skyrush.com> <20080824010231.GA26030@foursquare.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080824010231.GA26030@foursquare.net>
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1209
Lines: 30

On Sat, Aug 23, 2008 at 09:02:32PM -0400, Chris Frey wrote:
> On Sat, Aug 23, 2008 at 11:52:02AM -0600, Joe Peterson wrote:
> > Vegard Nossum wrote:
> > >> I've noticed that on my Debian stable system, I can now see Ctrl-C characters
> > >> when using an xterm.  I've checked the stty settings and nothing seems
> > >> different.
> > 
> > Vegard, thanks for forwarding this to me.
> > 
> > Chris, yes, what you are now seeing on the newer kernel is correct.
> 
> Thanks guys.  I was not aware of this change before asking.  The change
> makes sense.  I wasn't having any problems with it, just wondering where
> it came from.
> 
> Thanks for the enlightenment. :-)

I would not be surprized that it is what has caused delays for Ctrl-C
to take effect for some of us. As discussed in another thread on the
subject, the problem was relatively recent and not easy to reproduce.
Now we have a patch to try to revert if/when we finally get a reproducible
case.

Willy

--
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/