summaryrefslogtreecommitdiff
path: root/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment')
-rw-r--r--doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment b/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment
new file mode 100644
index 00000000..72315aa0
--- /dev/null
+++ b/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2016-03-06T19:57:03Z"
+ content="""
+Managed to reproduce the hang once, and the ssh was indeed being run as
+bgProcess. However, I didn't manage to see what foreground process, if any,
+was running when that happened. And had no luck reproducing it again.
+
+I added some more `PROPELLOR_DEBUG` output around this, so it'll tell
+when a process is being run by fgProcess or bgProcess.
+"""]]