diff options
author | Ben Noordhuis <info@bnoordhuis.nl> | 2013-02-22 01:19:39 +0100 |
---|---|---|
committer | Ben Noordhuis <info@bnoordhuis.nl> | 2013-02-22 01:19:40 +0100 |
commit | 22d3eff8f46d336337aa5d9625f6d5be9104bcff (patch) | |
tree | 402fa76a25cf3385671f940f3c5e935d1d9554ad | |
parent | ef945219090de0c04884528f4113435499cc8ec3 (diff) | |
download | node-new-22d3eff8f46d336337aa5d9625f6d5be9104bcff.tar.gz |
doc: add note about child process line buffering
Fixes #4808.
-rw-r--r-- | doc/api/child_process.markdown | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index 7c08424531..913a376363 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -6,7 +6,9 @@ Node provides a tri-directional `popen(3)` facility through the `child_process` module. It is possible to stream data through a child's `stdin`, `stdout`, and -`stderr` in a fully non-blocking way. +`stderr` in a fully non-blocking way. (Note that some programs use +line-buffered I/O internally. That doesn't affect node.js but it means +data you send to the child process is not immediately consumed.) To create a child process use `require('child_process').spawn()` or `require('child_process').fork()`. The semantics of each are slightly |