I usually get about 80% of my advertised DSL speed with scp. I can only suspect that there was some serious network congestion going on somewhere along the path, or otherwise crappy connection resulting in packet loss/retransmissions.
I use rsync -vvzSauEe 'ssh -p 22' --delete --progress --stats 'remote domain name:/full/path/to/source directory/' '/full/path/to/local destination' all the time with no problem, as well as the appropriately modified version to rsync in the reverse (upload) direction, to tunnel rsync through ssh. See man rsync to see what all the options do.
You are aware, I assume, that if the remote pathname has white space in it, you need to quote the whole path and escape any white space with preceding backslashes, as I have shown in the above rsync example, right? Same holds true for remote pathname for scp. Single tick quotes enclosing pathnames with white space works fine for the local side, as does no quotes but escaped white space.
Issuing a ctrl-c at the local computer should have killed your scp and I am not aware of rogue elements being left on the remote computer when doing so. Maybe ⌘q-ing Terminal in the middle of an active scp did it.
I use rsync -vvzSauEe 'ssh -p 22' --delete --progress --stats 'remote domain name:/full/path/to/source directory/' '/full/path/to/local destination' all the time with no problem, as well as the appropriately modified version to rsync in the reverse (upload) direction, to tunnel rsync through ssh. See man rsync to see what all the options do.
You are aware, I assume, that if the remote pathname has white space in it, you need to quote the whole path and escape any white space with preceding backslashes, as I have shown in the above rsync example, right? Same holds true for remote pathname for scp. Single tick quotes enclosing pathnames with white space works fine for the local side, as does no quotes but escaped white space.
Issuing a ctrl-c at the local computer should have killed your scp and I am not aware of rogue elements being left on the remote computer when doing so. Maybe ⌘q-ing Terminal in the middle of an active scp did it.
Scp Client For Mac
WinSCP by Martin Prikryl is one of the most popular, powerful and safe FTP (File Transfer Protocol) clients, but when you start working under Mac OS X, it is no longer a viable solution. If you need an application similar to WinSCP for Mac, you can check this list of alternatives to find a replacement.
Scp For Mac Os X
- WinSCP 5.17 is a major application update. New features and enhancements include: Improvements to sessions and workspace management, so that WinSCP can now easily restore tabs that were open when it was last closed. Hardware-accelerated AES. Extension Archive and Download to archive remote files and download the archive.
- Only solution which allows the use of scp -3 from and to servers with ssh listeners on different ports. Scp -3 -P 123 server1:/file -P 456 server2:/file or similar alternatives wouldn't work, scp assumed the same port across both servers – user88595 Jan 4 '19 at 13:10.