1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: add notes to child_process.fork() and .exec()

Browse Source 
Adds notes about the difference to their POSIX counterparts.

PR-URL: https://github.com/nodejs/io.js/pull/1718
Fixes: https://github.com/nodejs/io.js/issues/224
Reviewed-By: Roman Reiss <me@silverwind.io>
This commit is contained in:
Rich Trott 2015-05-16 19:33:13 -07:00 committed by Roman Reiss
parent 5773438913
commit 86dd244d9b
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/api/child_process.markdown
View File

@ -586,6 +586,8 @@ if it runs longer than `timeout` milliseconds. The child process is killed with
amount of data (in bytes) allowed on stdout or stderr - if this value is
exceeded then the child process is killed.
*Note: Unlike the `exec()` POSIX system call, `child_process.exec()` does not replace
the existing process and uses a shell to execute the command.*
### child_process.execFile(file[, args][, options][, callback])
@ -645,6 +647,9 @@ done with care and by default will talk over the fd represented an
environmental variable `NODE_CHANNEL_FD` on the child process. The input and
output on this fd is expected to be line delimited JSON objects.
*Note: Unlike the `fork()` POSIX system call, `child_process.fork()` does not clone the
current process.*
## Synchronous Process Creation
These methods are **synchronous**, meaning they **WILL** block the event loop,