From 0fff28623cd12e99a45d6002192d62f1545340df Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 9 May 2017 14:02:48 -0400 Subject: response; update man page --- ...nt_23_e5e7ec9fbafe5e0429161b977e483752._comment | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/sync/comment_23_e5e7ec9fbafe5e0429161b977e483752._comment (limited to 'doc/sync/comment_23_e5e7ec9fbafe5e0429161b977e483752._comment') diff --git a/doc/sync/comment_23_e5e7ec9fbafe5e0429161b977e483752._comment b/doc/sync/comment_23_e5e7ec9fbafe5e0429161b977e483752._comment new file mode 100644 index 000000000..cfb62ba11 --- /dev/null +++ b/doc/sync/comment_23_e5e7ec9fbafe5e0429161b977e483752._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 23""" + date="2017-05-09T17:52:11Z" + content=""" +@mario, great question! (Not the best place for such a question, start a +thread on the forum next time..) + +git-annex does use rsync when transferring files between ssh remotes. +Rsync normally goes over ssh, and it might be better to enable compression +at the ssh level. For example, I have "Compression yes" in `~/.ssh/config` + +I think that the reason your annex-rsync-upload-options setting broke +it is that rsync needs --compress to be passed on to the other +rsync process (in the remote repository), and that is run via +git-annex-shell, which has a whitelist of options it will pass to rsync. +Passing arbitrary options to rsync could allow unwanted behavior +when git-annex-shell is being used as a security barrier. And --compress is +one of the options that both the rsync sender and receiver have to agree +on for the rsync protocol to work. + +I have added a note to the man page about this limitation of what +the rsync-options settings can be used to do. +"""]] -- cgit v1.2.3