diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-09-13 19:28:57 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-09-13 19:28:57 -0400 |
| commit | ac67b4ed00928b9399fa4c7147a9c0fcbe0ace5f (patch) | |
| tree | 9fc70bbb76afb930999a6504b9a1571236d035c3 /doc/bugs | |
| parent | 5573911d25e51c3434f1666ee415a0c0781714fc (diff) | |
| parent | 8b9c1b1b508e0764f475662f04725da617c384c3 (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
Diffstat (limited to 'doc/bugs')
| -rw-r--r-- | doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment b/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment new file mode 100644 index 000000000..0cba1a693 --- /dev/null +++ b/doc/bugs/ControlPath_too_long_for_Unix_domain_socket/comment_1_60f58e205604eebe668b1e05dcfbf9a7._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.30" + subject="comment 1" + date="2012-09-13T22:00:53Z" + content=""" +You can work around the ControlPath too long by running in your git repo: + +git config annex.sshcaching false + +While I could reproduce that part of your problem, I did *not* see any data actually be transferred when the ControlPath was too long. For example: + +<pre> +joey@gnu:~/tmp/t/1>git annex transferkey --to foo SHA256E-s29--66ffceb8b7a1af9c2eb896f26fb8f3bdab0a606da59a7a2d71ae4f7d78ad13c4/SHA256E-s29--66ffceb8b7a1af9c2eb896f26fb8f3bdab0a606da59a7a2d71ae4f7d78ad13c4 + +ControlPath too long +rsync: connection unexpectedly closed (0 bytes received so far) [sender] +rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] + + rsync failed -- run git annex again to resume file transfer +failed +git-annex: transferkey: 1 failed +</pre> +"""]] |