Disable ssh connection caching if the path to the control socket would be too long (and use relative path to minimise path to the control socket).
This commit is contained in:
parent
60c31afc38
commit
5573911d25
3 changed files with 29 additions and 2 deletions
|
@ -41,4 +41,10 @@ stdout snippet from git-annex webapp:
|
|||
|
||||
This data appears on both the sending and receiving git-annex stdout. At least for the initial sync. For later syncs it only appears on the sender, though the client system is using a lot of resources.
|
||||
|
||||
|
||||
> I've made git-annex detect if the control path would be too long,
|
||||
> and disable ssh connection caching. It also tries a relative path
|
||||
> to the file, which tends to make it shorter, and I think would
|
||||
> keep ssh connection caching working in your example.
|
||||
>
|
||||
> Please test and see if it works, and also if the "looping" problem
|
||||
> still happens. --[[Joey]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue