Messages in this thread | | | Date | Mon, 25 Aug 2008 16:13:54 +0200 | From | Willy Tarreau <> | Subject | Re: Visible Ctrl-C in latest kernels |
| |
Hi Joe,
On Mon, Aug 25, 2008 at 08:00:07AM -0600, Joe Peterson wrote: > Willy Tarreau wrote: > >>> 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. > > It seems very unlikely that the echo has anything to do with it, other > than making the problem more visible. See this post: > > http://marc.info/?l=linux-kernel&m=121526224222656&w=2
possible, indeed.
> And to what patch of yours are you referring?
not mine, I was speaking about your patch of 2008/02/06 which was talked about earlier in this thread. I was thinking that it was possible that the signal got delayed when it was hard to print ^C because the output was already busy spewing a stream of data. Maybe I'm wrong, but I mean it does not cost much to try to revert this patch when the problem is encountered. And I keep in mind that it is possible, as you say, that your patch only makes the problem more visible.
Regards, Willy
| |