From 67615bda8dc53d4987748b2e82e3fa11a86bba99 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 24 Sep 2018 15:05:41 -0400 Subject: [PATCH] thoughts --- ..._1713d56b81db533db4532f2a79250c87._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/bugs/get_over_ssh_fails_with___fd__58__19__58___hClose__58___resource_vanished/comment_4_1713d56b81db533db4532f2a79250c87._comment diff --git a/doc/bugs/get_over_ssh_fails_with___fd__58__19__58___hClose__58___resource_vanished/comment_4_1713d56b81db533db4532f2a79250c87._comment b/doc/bugs/get_over_ssh_fails_with___fd__58__19__58___hClose__58___resource_vanished/comment_4_1713d56b81db533db4532f2a79250c87._comment new file mode 100644 index 0000000000..35eadd4a57 --- /dev/null +++ b/doc/bugs/get_over_ssh_fails_with___fd__58__19__58___hClose__58___resource_vanished/comment_4_1713d56b81db533db4532f2a79250c87._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2018-09-24T18:37:08Z" + content=""" +The only new change in 6.20180913 that might somehow affect this is +[[!commit b18fb1e343e9654207fbebacf686659c75d0fb4c]]. But I don't see how +it could really. + +Since ssh seems to be displaying a motd when running a noninteractive +command, I think that git-annex must be seeing that motd where it +expects to see the P2P protocol. + +Although it may be that ssh -T avoids the motd display. (But unfortunately +your transcript using -T trims out exactly that part!) I didn't think ssh +normally displays motd when not running a login shell. Perhaps it's +something to do with your shell and not ssh. + +git-annex will fall back to not using p2pstdio, but only if the command +exits nonzero without ssh sending anything to stdout. +"""]]