3 ms·
> so if you hit ^C it will abort stuff even if the screen is scrolling I might be wrong, but AFAIK the fact that your terminal isn't handling this correctly al
by saurik 14y ago
> so if you hit ^C it will abort stuff even if the screen is scrolling
I might be wrong, but AFAIK the fact that your terminal isn't handling this correctly already is due to a flow control setup problem somewhere in the chain (probably the terminal itself, as usually the server-side components are the most ancient): if your local console is only able to download and display and scroll data at a certain rate, it should "push back" on the server to get it to send you data at a slower rate, which in turn will push back on the terminal. When setup correctly, this flows all the way back to the original application, which will itself slow down whatever it is that it is doing.
- zobzu 14y agoits tcp congestion issues. ^C will work just fine locally. it would also be ok if there were 2 tcp channels. or. udp. ;)
- saurik 14y agoI don't mean locally: I mean that if you have all of your flow control stuff setup correctly, you shouldn't ever end up in the situation of "I hit ctrl-C to try to stop the massive stream of text, but this text was actually generated a minute ago and was streamed to me in a massive 10MB block and buffered in a bunch of sockets, so my ctrl-C is meaningless".