From a184dbcb2c689f22c8c2c616ab5734818a8f25aa Mon Sep 17 00:00:00 2001 From: cjihrig Date: Sat, 4 Nov 2017 10:36:41 -0400 Subject: [PATCH] doc: update subprocess.killed This commit changes the wording of subprocess.killed to reflect that a child process was successfully signaled, and not necessarily terminated. Fixes: https://github.com/nodejs/node/issues/16747 PR-URL: https://github.com/nodejs/node/pull/16748 Reviewed-By: Luigi Pinca Reviewed-By: Rich Trott Reviewed-By: James M Snell --- doc/api/child_process.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/api/child_process.md b/doc/api/child_process.md index 48b8f395b238f5..8be21a1d07d908 100644 --- a/doc/api/child_process.md +++ b/doc/api/child_process.md @@ -1044,10 +1044,11 @@ added: v0.5.10 --> * {boolean} Set to `true` after `subprocess.kill()` is used to successfully - terminate the child process. + send a signal to the child process. -The `subprocess.killed` property indicates whether the child process was -successfully terminated using `subprocess.kill()`. +The `subprocess.killed` property indicates whether the child process +successfully received a signal from `subprocess.kill()`. The `killed` property +does not indicate that the child process has been terminated. ### subprocess.pid