From 65f21edcac2e42e1300aeb9e912f267e1e71419c Mon Sep 17 00:00:00 2001 From: anarcat Date: Thu, 7 Feb 2019 21:10:19 +0000 Subject: [PATCH] Added a comment --- .../comment_2_4f417206d5d83bd456c8e501ae272cba._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/leaves_many_stray_processes_on_remote_server/comment_2_4f417206d5d83bd456c8e501ae272cba._comment diff --git a/doc/bugs/leaves_many_stray_processes_on_remote_server/comment_2_4f417206d5d83bd456c8e501ae272cba._comment b/doc/bugs/leaves_many_stray_processes_on_remote_server/comment_2_4f417206d5d83bd456c8e501ae272cba._comment new file mode 100644 index 0000000000..279605be7e --- /dev/null +++ b/doc/bugs/leaves_many_stray_processes_on_remote_server/comment_2_4f417206d5d83bd456c8e501ae272cba._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="anarcat" + avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7" + subject="comment 2" + date="2019-02-07T21:10:19Z" + content=""" +you'll notice that some of those processes have been hanging out there for days. i believe the TCP sockets are long gone, at least their parent SSH process are gone. this is why i related this to the \"kill git-annex assistant on logout\" - but since git-annex doesn't do setsid anymore (right?) I don't understand why those process could be left there without a parent... especially since that's on the server-side, which has a (relatively) up to date git-annex version... +"""]]