From 9af22fb9838f7889a145bc4e10089be526f60a05 Mon Sep 17 00:00:00 2001 From: Aaron Ball Date: Wed, 30 Dec 2020 09:00:41 -0700 Subject: bash waitpid function:Fix rst list --- posts/bash:waitpid_function.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/posts/bash:waitpid_function.rst b/posts/bash:waitpid_function.rst index 350dee6..dae296b 100644 --- a/posts/bash:waitpid_function.rst +++ b/posts/bash:waitpid_function.rst @@ -56,17 +56,17 @@ knowledge could be solved easily and in a portable, reproducible, and maintainable manner. The problems are more than just technical as well. Here are the problems that I see. -. It doesn't ensure the process stops before proceeding +* It doesn't ensure the process stops before proceeding -. Kill signal 0 does nothing except allow for error checking (eg: if the +* Kill signal 0 does nothing except allow for error checking (eg: if the process is still running). Check ``man 1 kill`` for more information. TLDR; Kill -0 shouldn't be used for asking a process to stop. -. The pid status check relies on the output from a subshell +* The pid status check relies on the output from a subshell -. There is no contingency for when the process won't shut down. +* There is no contingency for when the process won't shut down. -. The code exists outside of a function, and thus is more difficult to reuse +* The code exists outside of a function, and thus is more difficult to reuse Writing a waitpid function -- cgit v1.2.3