Commit f4bc12d
doc: note message event listeners ref IPC channels
The IPC channel is referenced with the message event too.
PR-URL: #11494
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent f0c7c7f commit f4bc12d
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -536,9 +536,9 @@ spawn('prg', [], { stdio: ['pipe', null, null, null, 'pipe'] }); | |||
| 536 | 536 | *It is worth noting that when an IPC channel is established between the | |
| 537 | 537 | parent and child processes, and the child is a Node.js process, the child | |
| 538 | 538 | is launched with the IPC channel unreferenced (using `unref()`) until the | |
| 539 | - child registers an event handler for the `process.on('disconnected')` event. | ||
| 540 | - This allows the child to exit normally without the process being held open | ||
| 541 | - by the open IPC channel.* | ||
| 539 | + child registers an event handler for the `process.on('disconnect')` event | ||
| 540 | + or the `process.on('message')` event.This allows the child to exit normally | ||
| 541 | + without the process being held open by the open IPC channel.* | ||
| 542 | 542 | ||
| 543 | 543 | See also: [`child_process.exec()`][] and [`child_process.fork()`][] | |
| 544 | 544 | ||
0 commit comments