diff options
author | https://me.yahoo.com/a/f.0S5jJlgJMHgMV6G2fLXzkhRCQtDAAxRe8-#81b3e <Scott@web> | 2013-10-09 21:19:09 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2013-10-09 21:19:09 +0000 |
commit | f02f0aeb1c8d7ac5246cbe4802b2fba342d82f8e (patch) | |
tree | d1c613fbe11d71e540f755b66b706d16cee4502f /doc | |
parent | d23b84c5b703ee5246b030aad2d7358fe4107c30 (diff) |
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/git_annex_sync_dies___40__sometimes__41__.mdwn | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/git_annex_sync_dies___40__sometimes__41__.mdwn b/doc/forum/git_annex_sync_dies___40__sometimes__41__.mdwn new file mode 100644 index 000000000..84f9d1125 --- /dev/null +++ b/doc/forum/git_annex_sync_dies___40__sometimes__41__.mdwn @@ -0,0 +1,22 @@ +I've set up git annex on my laptop and on a remote server using the gitolite v3 git-annex branch. +When I 'git annex sync' from my laptop (mac OSX) to the server, and 'git annex copy . --to server' all works fine. + +Later, I tried to clone the repository on another machine (linux 2.6.32). again all is well. I 'git annex init' in the new clone and then try to 'git annex sync' -- now I run into problems. + +Specifically, the first request for the configlist (when I do 'git annex --debug sync' all is fine until the configlist request) somehow breaks and my ssh session shows: + +muxserver_listen bind(): Input/output error + +This seems to confuse the client, who now believes that git annex is not installed on the server (it is). + +If I issue the same command as git annex via ssh, all seems to work ok with the caveats below: + +I have a feeling it's related to the -o 'ControlPersist=yes' argument that git-annex appears to be giving ssh. If I include this option when I run via ssh, ssh dies: + +>ssh git@server -o "ControlMaster=auto" -o "ControlPersist=yes" "git-annex-shell 'configlist' '/~/PRJ'" +command-line: line 0: Bad configuration option: ControlPersist + + +(note that it appears to be ok to leave "ControlMaster=auto" in). + +any thoughts? |