As with many things in node, child processes can emit an error event. Add a listener for that and you will be able to catch it (no try-catch needed): var spawn = require(‘child_process’).spawn; var child = spawn(‘foo’); child.on(‘error’, function(err) { console.log(‘Oh noez, teh errurz: ‘ + err); });
There is now a power tool that lets you attach to child process: Introducing The Child Process Debugging Power Tool
Use exit event for the child process. var child = require(‘child_process’).exec(‘python celulas.py’) child.stdout.pipe(process.stdout) child.on(‘exit’, function() { process.exit() }) PS: It’s not really a duplicate, since you don’t want to use sync code unless you really really need it.
You need to pass also \n symbol to get your command work: var spawn = require(‘child_process’).spawn, child = spawn(‘phantomjs’); child.stdin.setEncoding(‘utf-8’); child.stdout.pipe(process.stdout); child.stdin.write(“console.log(‘Hello from PhantomJS’)\n”); child.stdin.end(); /// this call seems necessary, at least with plain node.js executable
If you can use node’s built in child_process.spawn, you’re able to send a SIGINT signal to the child process: var proc = require(‘child_process’).spawn(‘mongod’); proc.kill(‘SIGINT’); An upside to this is that the main process should hang around until all of the child processes have terminated.
Just use : pgrep -P $your_process1_pid
I think you’re misunderstanding what a fork does. When you successfully fork, you’re creating a subprocess, independent from the process you started with, to continue doing work. Because it’s a separate process, it has its own memory, variables, etc., even though some of these started out as copies from the parent process. So you’re setting … Read more
Here is how to fork 10 children and wait for them to finish: pid_t pids[10]; int i; int n = 10; /* Start children. */ for (i = 0; i < n; ++i) { if ((pids[i] = fork()) < 0) { perror(“fork”); abort(); } else if (pids[i] == 0) { DoWorkInChild(); exit(0); } } /* … Read more
as it happens I have a bit of C#/WMI code lying around that kills all processes spawned by a specified process id, recursively. the killing is obviously not what you want, but the finding of child processes seems to be what you’re interested in. I hope this is helpful: private static void KillAllProcessesSpawnedBy(UInt32 parentProcessId) { … Read more
You open your long-running process and keep a pipe to it. So you expect to talk to it. When yor launcher script exits, you can no longer talk to it. The long-running process receives a SIGPIPE and exits. The following just worked for me (Linux, Python 2.7). Create a long-running executable: $ echo “sleep 100” … Read more