From 4d09233efd8ad7a238f8002d1aa4cfe3a37013e6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 20:54:21 -0400 Subject: update --- ...ent_8_b5ba54711a869076fdf78f81f2f5c70d._comment | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_8_b5ba54711a869076fdf78f81f2f5c70d._comment (limited to 'doc') diff --git a/doc/forum/Weird_SSH_issue/comment_8_b5ba54711a869076fdf78f81f2f5c70d._comment b/doc/forum/Weird_SSH_issue/comment_8_b5ba54711a869076fdf78f81f2f5c70d._comment new file mode 100644 index 00000000..f5110479 --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_8_b5ba54711a869076fdf78f81f2f5c70d._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2016-03-06T23:47:58Z" + content=""" +I modified spin', adding this before its final ssh: + + async $ createProcessForeground $ proc "sleep" ["500"] + +This more or less replicates the problem reliably; the remote propellor +runs but nothing gets displayed for 500 seconds until the sleep process +is done. At which point the whole buffered output appears. Use cat instead +and it'll hang forever. + +Of course, that means `ps fax` shows propellor with sleep and ssh as +child processes. If only ssh shows as a child process and nothing else +when the problem naturally occurs, then that's a different problem +than what I was able to replicate. + +Anyway, this seems too fragile to leave like this even though +nothing run on the way to a ssh should run for very long. +So, I'm making the ssh be run forced to the foreground, which will +certianly avoid all such problems. +"""]] -- cgit v1.2.3