doc: refine child_process detach behaviour #5330
Conversation
ChALkeR
added
child_process
| 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. | ||
| *Note: that detaching process works highly platform specific* |
There was a problem hiding this comment.
Perhaps: *Note that detaching a process is platform specific.* ... also would be good to list the platform specific differences here.
|
@nodejs/documentation |
|
enhanced upon @jasnell's comment. Note, the reason I wanted to mention the specific behaviour down there again is because copy-pasting the either of the code snippet will likely lead to unwanted behaviour depending on which platform you are. The API isn't really consistent there, which of course is OS'es nature of different process implementations. I also removed |
| 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. | ||
| *Note: The behavior of detaching a process is platform specific, as described in |
There was a problem hiding this comment.
Looking at the new layout of the file, this note seems unnecessary.
|
LGTM with a few comments. |
this adds an example of a long running node process that actually executes node code. Also it mentions the not to harmonic detach behaviours of the different platforms, whereas detaching on unix requires ignoring the child_process' stdio explicitely.
|
@cjihrig addressed your comments. Content-wise I just omitted the |
|
Cool. Thanks. If @jasnell is good with it, we can land this. |
|
LGTM |
this adds an example of a long running node process that actually executes node code. Also it mentions the not to harmonic detach behaviours of the different platforms, whereas detaching on unix requires ignoring the child_process' stdio explicitely. PR-URL: #5330 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
|
Landed in 82c2996 |
this adds an example of a long running node process that actually executes node code. Also it mentions the not to harmonic detach behaviours of the different platforms, whereas detaching on unix requires ignoring the child_process' stdio explicitely. PR-URL: #5330 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
this adds an example of a long running node process that actually executes node code. Also it mentions the not to harmonic detach behaviours of the different platforms, whereas detaching on unix requires ignoring the child_process' stdio explicitely. PR-URL: #5330 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This adds an example of a long running node process that actually
executes node code.
Also it mentions the not to harmonic detach behaviours of the
different platforms, which might also invite some core work.
I felt this to be necessary after researching for #5146, whereas the the behaviour of detaching seems highly inconsistent and very untransparent for the user.
/cc @nodejs/documentation