tag:blogger.com,1999:blog-1541371521224765784.post6101101420251899081..comments2020-02-19T00:57:28.061-08:00Comments on <center>Field Notes of an Audacious Amateur</center>: 10th installment: resume an scp file transferwayover13http://www.blogger.com/profile/13204644261961607009noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1541371521224765784.post-36316403696264451262013-01-11T09:41:46.784-08:002013-01-11T09:41:46.784-08:00Currently (and since around 2004) the default tran...Currently (and since around 2004) the default transfer protocol in rsync *IS* ssh. There is no need for the '-e ssh' unless you directly connect to a remote rsync daemon. In that case rsync will use plain tcp. As seen by your code above you are not doing that though so this is a non-issue for you code and you can drop the '-e ssh' as it is default. Leave the '.ssh/config' though as that would still be needed to instruct ssh how to connect to that host.<br /><br /><br />As per 'man rsync':<br />There are two different ways for rsync to contact a remote system: using a remote-shell program as the transport (such as<br />ssh or rsh) or contacting an rsync daemon directly via TCP. The remote-shell transport is used whenever the source or<br />destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly<br />happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an<br />rsync:// URL is specified (see also the “USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION” section for an excep-<br />tion to this latter rule).<br /><br />dadreggorshttps://www.blogger.com/profile/11773304039963225079noreply@blogger.com