Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9223947
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T04:11:47+00:00 2026-06-18T04:11:47+00:00

I have been tinkering around with node a little, and while trying to learn

  • 0

I have been tinkering around with node a little, and while trying to learn the child_process module, I ran into a problem. I was attempting to serialize many calls to ‘ps -eF | grep ssh’, but it crashes on my system with the error below. So two questions. First, is there a better way to do what I am attempting without a library? Second, why isn’t it working 🙂

events.js:71
        throw arguments[1]; // Unhandled 'error' event
                       ^
Error: This socket is closed.
    at Socket._write (net.js:519:19)
    at Socket.write (net.js:511:15)
    at Socket.<anonymous> (/home/me/tmp/test.js:10:16)
    at Socket.EventEmitter.emit (events.js:96:17)
    at Pipe.onread (net.js:397:14)
function callpsgrep(callback) {
  var spawn = require('child_process').spawn,
      ps    = spawn('ls', ['-la']),
      grep  = spawn('grep', ['bananas']);

  ps.stdout.on('data', function (data) {
    grep.stdin.write(data);
  });

  ps.stderr.on('data', function (data) {
    console.log('ps stderr: ' + data);
  });

  ps.on('exit', function (code) {
    if (code !== 0) {
      console.log('ps process exited with code ' + code);
    }
    grep.stdin.end();
  });

  grep.stdout.on('data', function (data) {
    console.log('' + data);
  });

  grep.stderr.on('data', function (data) {
    console.log('grep stderr: ' + data);
  });

  grep.on('exit', function (code) {
    if (code !== 0) {
      console.log('grep process exited with code ' + code);
    }
    callback();
  });
}

function series(i) {
  if (i < 1000) {
    callpsgrep( function() {
      return series(i+1);
    });
  }
}
series(0);
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T04:11:48+00:00Added an answer on June 18, 2026 at 4:11 am

    Close grep’s stdin on the close event instead of the exit event.

    ps.on('exit', function (code) {
      if (code !== 0) {
        console.log('ps process exited with code ' + code);
      }
    });
    
    ps.on('close', function (code) {
      grep.stdin.end();
    });
    

    Although not very well documented I read the following in the help file.

    Event: ‘exit’

    Note that the child process stdio streams might still be open.

    Event: ‘close’#

    This event is emitted when the stdio streams of a child process have all terminated. This is distinct from ‘exit’, since multiple processes might share the same stdio streams.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have been tinkering around with PDF::API2 and i am facing a problem, create
I've been tinkering with a regex answer by yukondude with little success. I'm trying
I have been tinkering around with ServiceStack to expose some web services and have
I have a private project I've been tinkering with for a while. I'm thinking
I am completely new to Batch files and have been tinkering around with simple
I've been tinkering around trying to make an AI player for the popular card
I have been tinkering on NodeJS for a while now. I still don't seem
I've been tinkering around, and reading through what little Wiki information that I could
I have been tinkering around with OOP and seeing how to go about doing
I'm new to HTML5/Canvas/Game programming, but have been tinkering around with it after reading

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.