When downloading a file and the connection hangs due to crappy wifi, sftp just says "0.0 KB/s - stalled -". I hit ^C to kill it, but it just prints "Interrupt" and doesn't do anything, no matter how many times I hit ^C or how long I wait. Is this expected behavior? Or am I expected to kill the ssh connection itself with "~."?
On Sat, 31 Jul 2010, Ray Lai wrote:> When downloading a file and the connection hangs due to crappy wifi, > sftp just says "0.0 KB/s - stalled -". I hit ^C to kill it, but it > just prints "Interrupt" and doesn't do anything, no matter how many > times I hit ^C or how long I wait. Is this expected behavior? Or > am I expected to kill the ssh connection itself with "~."?When you interrupt a sftp transfer, it will wait for the server to drain all its outstanding requests so it remains in a clean state to issue another request. If you really need to Kill It Right Now, use SIGQUIT (ctrl-\ usually). -d
On 31/07/10 5:25 PM, Ray Lai wrote:> When downloading a file and the connection hangs due to crappy wifi, > sftp just says "0.0 KB/s - stalled -". I hit ^C to kill it, but it > just prints "Interrupt" and doesn't do anything, no matter how many > times I hit ^C or how long I wait. Is this expected behavior? Or > am I expected to kill the ssh connection itself with "~."?What version of OpenSSH is this and on what platform? It sounds a lot like https://bugzilla.mindrot.org/show_bug.cgi?id=1590 which was fixed in the 5.4 release. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.