From 044da47353ea191f8521307abe1cd5c06f28efa2 Mon Sep 17 00:00:00 2001 From: Adrian Lang Date: Wed, 14 Aug 2013 21:31:33 +0200 Subject: [PATCH] doc: correct check for failed child_process.spawn Since 0.10.x, exec failures are no longer signaled through stderr, but rather as error events. Signed-off-by: Fedor Indutny --- doc/api/child_process.markdown | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index e1d6c1f852..ea90331a21 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -378,11 +378,8 @@ Example of checking for failed exec: var spawn = require('child_process').spawn, child = spawn('bad_command'); - child.stderr.setEncoding('utf8'); - child.stderr.on('data', function (data) { - if (/^execvp\(\)/.test(data)) { - console.log('Failed to start child process.'); - } + child.on('error', function (err) { + console.log('Failed to start child process.'); }); Note that if spawn receives an empty options object, it will result in