From b809f529d52e78043c675961b83e16b1085815cb Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 16:44:03 -0400 Subject: comment --- .../comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment 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. +"""]] -- cgit v1.2.3