From 38c7ee380d8fcf2f64445fb21aefe6f75a0b06fe Mon Sep 17 00:00:00 2001 From: Kyle Smith Date: Wed, 7 Oct 2015 16:03:21 -0700 Subject: [PATCH] Clarify the use of `option.detached` This paragraph conveys that detached child processes do not stay running in the background in general. Instead clarify that this refers to the parent process exiting before the detached child process is complete. --- doc/api/child_process.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index ab911acf22a5aa..d4583459a3bd6f 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -535,9 +535,10 @@ file: child.unref(); When using the `detached` option to start a long-running process, the process -will not stay running in the background unless it is provided with a `stdio` -configuration that is not connected to the parent. If the parent's `stdio` is -inherited, the child will remain attached to the controlling terminal. +will not stay running in the background after the parent exits unless it is +provided with a `stdio` configuration that is not connected to the parent. +If the parent's `stdio` is inherited, the child will remain attached to the +controlling terminal. See also: `child_process.exec()` and `child_process.fork()`