mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment: git annex using the "wrong" ssh socket

Browse source
This commit is contained in:
tom_clune 2016-02-24 19:23:13 +00:00 committed by admin
parent a11aaf4f99
commit c6d0e3e62e
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
doc/tips/centralized_git_repository_tutorial/on_your_own_server/comment_1_ae5af47faf95f008f1b07dbed5181286._comment Normal file
View file

@ -0,0 +1,28 @@
[[!comment format=mdwn
username="tom_clune"
subject="git annex using the "wrong" ssh socket"
date="2016-02-24T19:23:13Z"
content="""
To avoid frequent typing of pin + RSA passcode + password, we typically establish an ssh control master just once. This works fine with regular git commands, but the git-annex command apparently try to create a different socket. Even that would be ok, except that apparently it is a new socket each time we enter a command.
With sufficient \"-vvvv\" we see things like:
...
debug1: Executing proxy command: exec ssh -l fred proxy.xxx.yyy direct host
...
(Note I have eliminated references to the actual machine names and userid's.)
If the command had instead been:
exec ssh -l fred proxy.xxx.yyy direct /home/fred/.ssh/master_host:22
everything would have worked fine. In fact, we are now using:
git config remote.origin.annex-ssh-options '-S /home/fred/.ssh/master_host:22'
and this eliminates the issue. But it would be nice if git annex could somehow automatically use
the pre-existing connection. Is there a better way to achieve this?
"""]]