daohualiuxiang
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: clarify child_process error behaviour 

Clarify that an 'error' event may or may not be followed by an 'exit'
event and that it's not safe to make assumptions either way.
archived-io.js-v0.10
Linus Unnebäck 2013-11-21 16:39:23 +01:00 committed by Ben Noordhuis
parent 71aabedad4
commit 953d7184ec
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/api/child_process.markdown
View File

@ -36,6 +36,10 @@ Emitted when:
2. The process could not be killed, or 2. The process could not be killed, or
3. Sending a message to the child process failed for whatever reason. 3. Sending a message to the child process failed for whatever reason.
Note that the `exit`-event may or may not fire after an error has occured. If
you are listening on both events to fire a function, remember to guard against
calling your function twice.
See also [`ChildProcess#kill()`](#child_process_child_kill_signal) and See also [`ChildProcess#kill()`](#child_process_child_kill_signal) and
[`ChildProcess#send()`](#child_process_child_send_message_sendhandle). [`ChildProcess#send()`](#child_process_child_send_message_sendhandle).