From fb2c4fca3ec5601af4048e960758157d7c644d39 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Sep 2015 15:51:21 -0400 Subject: followup --- ...mment_5_7be9e5912ef4165bf193f65f51b8216b._comment | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment (limited to 'doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment') diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment new file mode 100644 index 00000000..15c06336 --- /dev/null +++ b/doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2015-09-21T19:47:17Z" + content=""" +So here's the code that runs that ssh command: + + unlessM (boolSystem "ssh" (map Param $ cacheparams ++ ["-t", sshtarget, shellWrap runcmd])) $ + error "remote propellor failed" + +I'm surprised it didn't fail with the error. This seems to say that ssh +exited 0, but without running the command. + +Also, ssh seems to have decided to take down the shared connection of its +own accord, which seems strange. Normally it should leave the shared +connection open. + +If you're able to reproduce this reliably, look into whether making +`sshCachingParams` return [] and thus get rid of this ssh connection caching somehow avoids the problem? +"""]] -- cgit v1.2.3