From 0957b771da4c58f593f3ecaf194ffdd5c6d335a5 Mon Sep 17 00:00:00 2001 From: guilhem Date: Sun, 14 Apr 2013 00:10:49 +0200 Subject: Allow rsync to use other remote shells. Introduced a new per-remote option 'annex-rsync-transport' to specify the remote shell that it to be used with rsync. In case the value is 'ssh', connections are cached unless 'sshcaching' is unset. --- doc/git-annex.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc') diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index 60ce3a9ae..b9badce9b 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -943,6 +943,15 @@ Here are all the supported configuration settings. to or from this remote. For example, to force ipv6, and limit the bandwidth to 100Kbyte/s, set it to "-6 --bwlimit 100" +* `remote..annex-rsync-transport` + + The remote shell to use to connect to the rsync remote. Possible + values are `ssh` (the default) and `rsh`, together with their + arguments, for instance `ssh -p 2222 -c blowfish`; Note that the + remote hostname should not appear there, see rsync(1) for details. + When the transport used is `ssh`, connections are automatically cached + unless `annex.sshcaching` is unset. + * `remote..annex-bup-split-options` Options to pass to bup split when storing content in this remote. -- cgit v1.2.3