Messages in this thread | | | Date | Tue, 01 Jul 2008 06:07:32 -0600 | From | Joe Peterson <> | Subject | Re: Ctrl+C doesn't interrupt process waiting for I/O |
| |
Török Edwin wrote: > Thanks for the patch , the process seems to respond faster to Ctrl-C, > but I'll have to find a way to measure that reliably. > However ^C is not echoed anymore for me.
I found the same thing when I originally did the ^C echo patch. If isig() was used instead of the order specified (flush, echo, signal), the ^C did not echo reliably (i.e., it echoed on a tty console, but not in an xterm). isig() does the kill, then the flush.
Note that ^Z uses the same logic, so the fact that you are seeing this take effect more quickly is interesting.
I will try a few things today, but please experiment with various orderings of the calls and let me know what you find (and test the ^C echo in both tty console and xterm).
-Joe -- 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/
| |