npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

process_status

v0.0.2

Published

A utility to get process information for given process name

Downloads

4

Readme

process_status

I needed to display process information on a status page in a dashboard. From the command line I would type something like:

$ ps -ef | grep httpd
root      3199     1  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3252  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3253  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3254  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3255  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3256  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3257  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3258  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
apache    3259  3199  0 Sep17 ?        00:00:00 /usr/sbin/httpd
swright  10615  8615  0 14:51 pts/1    00:00:00 grep httpd

The process_status utility runs something like that with some formatting options and returns an object containing something like the following:

{ grep_str: 'httpd',
  user_format: [],
  pid: '3199',
  pgid: '3199',
  format_str: '%U%p%r%a',
  processes:
   [ 'root      3199  3199 /usr/sbin/httpd',
     'apache    3252  3199 /usr/sbin/httpd',
     'apache    3253  3199 /usr/sbin/httpd',
     'apache    3254  3199 /usr/sbin/httpd',
     'apache    3255  3199 /usr/sbin/httpd',
     'apache    3256  3199 /usr/sbin/httpd',
     'apache    3257  3199 /usr/sbin/httpd',
     'apache    3258  3199 /usr/sbin/httpd',
     'apache    3259  3199 /usr/sbin/httpd' ],
  format_array: [ 'user', 'pid', 'pgid', 'args' ],
  formatted_process_list:
   [ [ 'root', '3199', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3252', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3253', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3254', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3255', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3256', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3257', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3258', '3199', '/usr/sbin/httpd' ],
     [ 'apache', '3259', '3199', '/usr/sbin/httpd' ] ] }

You can then use the display the data using the processes array or for prettier output you can use the formatted_process_list array to generate a table and the format_array to generate table headers.

Usage:

/**
*  Finds a process based on the grep string
*  
*  @param  grep_str    a string that will be used to grep the process list
*  @param   user_format     an array of friendly strings that will be used to 
*                           get string formatters from the formatters array
*  @param   cb              callback  
*/
get_status(grep_str, user_format, cb)

To generate the formatted_process_list array

/**
* @param   status      A status object created by get_status
* @param   cb          A callback function
*/
process_status_data(status, cb)

See the test.js file for an implementation example.