From 7f96801642c732957581ce56166d09ad4aae8d46 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 20 Feb 2020 16:01:38 -0400 Subject: [PATCH] improve --- .../comment_8_b302f24d3234b1c46ed1566cfdf696fb._comment | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_8_b302f24d3234b1c46ed1566cfdf696fb._comment b/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_8_b302f24d3234b1c46ed1566cfdf696fb._comment index 28ce825ca2..cab6838e95 100644 --- a/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_8_b302f24d3234b1c46ed1566cfdf696fb._comment +++ b/doc/todo/more_extensive_retries_to_mask_transient_failures/comment_8_b302f24d3234b1c46ed1566cfdf696fb._comment @@ -53,7 +53,8 @@ different types of processes a remote might run. while it's being used, and then gets put back into the pool once it's idle again. So, register the pid as belonging to a thread when the thread removes it from the pool, and deregister it when the thread - returns it. + returns it. If the thread gets killed, don't add it back to the pool, + but instead kill the process. 3. All the rest. For these what's needed is some way to register the pid of the process that a thread starts as belonging to the thread,