summaryrefslogtreecommitdiff
path: root/doc/forum/Weird_SSH_issue
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/Weird_SSH_issue')
-rw-r--r--doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment10
-rw-r--r--doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment8
-rw-r--r--doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment15
-rw-r--r--doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment22
4 files changed, 55 insertions, 0 deletions
diff --git a/doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment b/doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment
new file mode 100644
index 00000000..0eb98f6c
--- /dev/null
+++ b/doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-03-06T17:00:02Z"
+ content="""
+I think I've been seeing this too, recently.
+
+I had not put together that it involves the ssh control socket.
+And am not 100% sure it does yet.
+"""]]
diff --git a/doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment b/doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment
new file mode 100644
index 00000000..0b545262
--- /dev/null
+++ b/doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="mithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a82"
+ nickname="mithrandi"
+ subject="comment 2"
+ date="2016-03-06T17:39:34Z"
+ content="""
+Yes, it's possible I misdiagnosed the problem; I've never had the issue spinning twice in a row, but there may be other factors at play.
+"""]]
diff --git a/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment b/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment
new file mode 100644
index 00000000..adc64e5d
--- /dev/null
+++ b/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-03-06T17:54:20Z"
+ content="""
+It also seemed to affect the first spin and not the second one when I was
+seeing it. But that was 1-2 weeks ago, and I am not currently reproducing
+the issue.
+
+If you can reproduce it consistently, it would be good to check if the
+concurrent output layer, which involves intercepting all command output and
+serializing it, might be involved. If you edit
+`src/Utility/Process/Shim.hs` and make it simply `import System.Process as X`
+and remove the other import, that will bypass the concurrent output layer.
+"""]]
diff --git a/doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment b/doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment
new file mode 100644
index 00000000..2ffdcbac
--- /dev/null
+++ b/doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2016-03-06T18:43:37Z"
+ content="""
+Added some debugging, I found that processes run by concurrent-output tend to
+alternate between running foreground and background. So, when the socket
+exists and is old, it will run one more process than otherwise to
+stop ssh on that socket, and this will change which run method is
+used for subsequent processes.
+
+However, it really shouldn't matter if a process starts in the background;
+concurrent-output shoud notice when the output lock frees up, and start
+displaying the processes's output.
+
+So, this theory explains why the ssh socket seems to be involved, perhaps,
+but it doesn't really explain what's happening to prevent the remote
+propellor output from being shown.
+
+Unless some other foreground process is hanging around and keeping
+the output lock. Or some bug in concurrent-output..
+"""]]