Tag Info

New answers tagged


A .sql file is generally plaintext. TCP intrinsically compresses plain text already, so if you use ssh -C, you're recompressing something that is already compressed. This not only takes more time, but also may actually make the raw data sent over the wire larger in terms of bits. Also, ssh is already encrypting things, adding compression and decompression ...


Compression and decompression take time, so it's a trade off. If you have a slow network connection, it's worth taking the time for compression. If you have a 1Gbps connection between two nodes, you're probably going to lose more time to compression than you'll gain from transferring less data.


nohup scp shinto@source:/home/data roose@target.example.com:/var/tmp/file stop temporarily the command with CTRL+z put on background the command, type: bg yo can check the process with: jobs


Full credit for this answer goes to http://superuser.com/a/602436/142948 You need the -3 option for scp: scp -3 one:/opt/bigfile.tar.gz two:/opt/bigfile.tar.gz -3: Copies between two remote hosts are transferred through the local host. Without this option the data is copied directly between the two remote hosts. ...


The easy way to do things through two layers of SSH is to hide the intermediate layer. Set up a ProxyCommand so that you can directly run ssh computer_name from the original client. Set up public key authentication and activate agent forwarding (ForwardAgent yes in ~/.ssh/config), so that you don't need to provide credentials explicitly to the intermediate ...


Set up a port a local port forward. For OpenSSH it would mean: $ ssh login@host -L 2222:computer_name:22 which causes any connectionns to port 2222 on localhost be forwarded to port 22 on computer_name via - and that is important here - host. Then follow $ scp -P 2222 computer_name_user@localhost:remote local Obviously this also allows you to connect ...

Top 50 recent answers are included