C[omp]ute

From: andrew cooke <andrew@...>

Date: Fri, 5 Aug 2011 14:44:20 -0400

I often have to work remotely, bouncing through ssh tunnels, sometimes with a
very poor connection.

In this particular case, I have an ssh tunnel from my main machine (block) to
the client, which is bound to port 2222 on block (and port 22 on the client's
machine).  I also have certificates configured so that no passwords are
necessary.

From a VM, also running on block, I can copy a file to the client with:

  scp -oPort=2222 local-file-path block:remote-file-path

However, for large files this fails before the copy is complete.  But I can
then resume it using rsync:

  rsync -P -e "ssh -oPort=2222" local-file-path block:remote-file-path

Which (after multiple attempts) gets the data across.

Andrew