Tag Info

New answers tagged


If it's not very sensitive data and your connection is safe enough, ssh into B and download straight from A via ftp. SSH will make your download considerably slower because of the encryption work overhead. If possible split the 100GB file in multiple ones, especially if the ftp server on A doesn't support download resume.


Something like: ssh user@serverB nohup wget -bqc ftp://path/largefile.tar.gz wget options: -b : run in background -q : quiet -c : resume broken download (means you can restart if it breaks) This runs wget in the background so (hopefully) if you exit the ssh shell it'll keep going. Ok, I think you need nohup to ensure that is the case when/if you ...


Try inserting a space before the destination, like this: robocopy "c:\transfer_this.txt" "z: \this.txt" notice the space after the destination "folder" z:.


You can't half-enable it - if you enable clipboard on the server-side, then anyone who log in (and, of course, enable it in the client) can use it both to copy from and to the server. You should look for some other remoting solution.


Quoting man ssh (which is the base used by scp): Compression is desirable on modem lines and other slow connections, but will only slow down things on fast networks. The problem is that compressing the data takes more time then just sending it over the network.

Top 50 recent answers are included