Timeline for Stopping output from a program run in SSH session NOW
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15, 2018 at 16:58 | answer | added | Saksham Sharma | timeline score: 1 | |
| Feb 6, 2018 at 22:01 | answer | added | Eric | timeline score: 1 | |
| Apr 13, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
|
|
| Feb 24, 2017 at 10:48 | comment | added | lmat - Reinstate Monica | The answers are unsatisfying. The gist is: the data that got queued up between when the command started outputting and when you press ^C is enough to keep your terminal program busy for several seconds. So it seems that the terminal program should be able to simply throw away data for a while...skip some bytes, something? | |
| Jul 27, 2016 at 4:46 | comment | added | gmatht | You could use mosh instead of ssh: mosh.mit.edu | |
| Jun 19, 2014 at 10:10 | answer | added | Hastur | timeline score: 1 | |
| S Jun 19, 2014 at 4:24 | history | suggested | TPS | CC BY-SA 3.0 |
kbd button format
|
| Jun 19, 2014 at 4:01 | review | Suggested edits | |||
| S Jun 19, 2014 at 4:24 | |||||
| Jun 19, 2014 at 1:07 | answer | added | Gilles 'SO- stop being evil' | timeline score: 3 | |
| Jun 18, 2014 at 18:58 | vote | accept | rr- | ||
| Jun 18, 2014 at 18:38 | answer | added | garethTheRed | timeline score: 4 | |
| Jun 18, 2014 at 18:36 | comment | added | psimon |
Just an idea: if you have some exact commands that you usually accidentally execute and they generate a lot of output, why not just append some aliases to .bashrc?
|
|
| Jun 18, 2014 at 18:32 | comment | added | Mark Plotnick |
You might try starting your xterm with the -j option, to enable jump scrolling. The basic problem is that the remote can send data faster than the terminal window can display it - by default, it has to bitblt the contents of the window every time a new line is printed. A whole lot of data can get buffered up by the time your Ctrl-C gets received by the remote system, and your terminal program will try to display all of it.
|
|
| Jun 18, 2014 at 18:28 | review | First posts | |||
| Jun 18, 2014 at 18:30 | |||||
| Jun 18, 2014 at 18:26 | answer | added | slm♦ | timeline score: 10 | |
| Jun 18, 2014 at 18:25 | comment | added | rr- | The server runs on Debian. Edited the question. Ctrl-O seems to do nothing as well. Perhaps it's the client thing? | |
| Jun 18, 2014 at 18:25 | history | edited | rr- | CC BY-SA 3.0 |
added 110 characters in body
|
| Jun 18, 2014 at 18:24 | comment | added | Mark Plotnick |
On which system are you running the actual programs that produce the output? Linux, Unix, or Windows? Linux and UNIX ought to accept Ctrl-O, which means "discard any output that is written to this terminal".
|
|
| Jun 18, 2014 at 18:11 | history | asked | rr- | CC BY-SA 3.0 |