From 8e37cb385d229f4497971c7f33e66ceb9c749116 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sat, 16 May 2015 19:33:13 -0700 Subject: [PATCH] child_process: note in docs that fork() and exec() are unrelated to Unix system calls of the same name --- doc/api/child_process.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index 19b2b9016fd5e0..af64e3141c5ecb 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -586,6 +586,7 @@ 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. +`child_process.exec()` is unrelated to the `exec()` system call in Unix-like operating systems. ### child_process.execFile(file[, args][, options][, callback]) @@ -645,6 +646,8 @@ 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. +`child_process.fork()` is unrelated to the `fork()` system call in Unix-like operating systems. + ## Synchronous Process Creation These methods are **synchronous**, meaning they **WILL** block the event loop,