Skip to content

Commit

Permalink
doc: add notes to child_process.fork() and .exec()
Browse files Browse the repository at this point in the history
Adds notes about the difference to their POSIX counterparts.

PR-URL: nodejs/node#1718
Fixes: nodejs/node#224
Reviewed-By: Roman Reiss <[email protected]>
  • Loading branch information
Trott authored and andrewdeandrade committed Jun 3, 2015
1 parent 0c4c2b5 commit 19fd6c1
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions doc/api/child_process.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -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])

Expand Down Expand Up @@ -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,
Expand Down

0 comments on commit 19fd6c1

Please sign in to comment.