From 73289afdab696dd757981da9220a800676209dbe Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 16 Mar 2020 14:37:57 -0400 Subject: [PATCH] comment --- ...t_15_ba2420e2d8f41dbdafc839246b8362aa._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_15_ba2420e2d8f41dbdafc839246b8362aa._comment diff --git a/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_15_ba2420e2d8f41dbdafc839246b8362aa._comment b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_15_ba2420e2d8f41dbdafc839246b8362aa._comment new file mode 100644 index 0000000000..fbf7436a2c --- /dev/null +++ b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_15_ba2420e2d8f41dbdafc839246b8362aa._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 15""" + date="2020-03-16T18:27:34Z" + content=""" +Re ControlPersist=yes, git-annex runs ssh -O stop on a socket file on exit, +unless some other git-annex process is also using that socket. So they don't +hangaround stale. By passing options to make ssh use other sockets, +you bypass that. + +I do see in https://github.com/datalad/datalad/pull/4265 +that you seem to have reproduced the hang without running git-annex at all? +Is that right? Seems to say not a git-annex bug. Perhaps some innocuous +change in behavior by git-annex, that tickles whatever the real problem is. +"""]]