From f203475eae2dc4fc5d52cb3ac716d633d46fb089 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 16 Mar 2020 13:12:18 -0400 Subject: [PATCH] comment --- ...nt_12_435c4cad7d3837aa09292642b983f041._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_12_435c4cad7d3837aa09292642b983f041._comment diff --git a/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_12_435c4cad7d3837aa09292642b983f041._comment b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_12_435c4cad7d3837aa09292642b983f041._comment new file mode 100644 index 0000000000..9b88697575 --- /dev/null +++ b/doc/bugs/enableremote_stuck_with_a_recentish_git-annex/comment_12_435c4cad7d3837aa09292642b983f041._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 12""" + date="2020-03-16T16:48:38Z" + content=""" +It seems to me that the process tree you pasted there comes from +the host where git-annex is running, and not the host that it sshes +to in order to run git-annex-shell. + +What I was suggesting is, if ssh $host git-annex-shell seems to be hanging, +it then makes sense to go look at $host and see if git-annex-shell is +running there, or has already run there (eg looking at +the ssh log). That bisects the problem space to one side or the other. +"""]] -- 2.30.2