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

killsome

v0.1.3

Published

Kill processes by name interactively (like killall, except that not necessarily all)

Downloads

18

Readme

killsome Dependency Status DevDependency Status

npm

Kill processes by name interactively (like killall, except that not necessarily all and interactive by design).

Processes are to be distinguished from one another by threads and subprocesses they forked (pstree output), as well as usual process parameters such as PID, launch time, etc.

CLI

Usage:  killsome [-<SIGNAL>] [option]... <name>

Options:
  --help         Print this message
  --version      Print version number
  --signal       Signal to be sent     [default: "TERM"]
  --pid, -p      Show PID              [default: true]
  --ppid, -P     Show PPID             [default: false]
  --user, -u     Show EUSER            [default: false]
  --command, -c  Show COMMAND          [default: false]
  --start, -s    Show START            [default: true]
  --cpu, -C      Show %CPU             [default: false]
  --mem, -M      Show %MEM             [default: false]
  --tty, -T      Show TTY              [default: false]
  --all          Show all

--signal accepts both numbers and symbolic names and also has a shorter form:

killsome --signal=9
killsome --signal KILL
killsome -KILL

Every boolean option can be negated with --no-, e.g. killsome --no-pid <name>.

Example

$ killsome fish

You will be presented with all found instances and process trees they are roots of.

0) pid=4808, start=23:26:18
fish---emacs

1) pid=5780, start=14:20:07
fish-+-emacs
     `-node-+-pstree
            `-{node}

2) pid=6097, start=23:46:26
fish---python2.7---{python2.7}

3) pid=9985, start=00:33:45
fish---9*[{fish}]

4) pid=13113, start=16:14:26
fish

5) pid=14896, start=16:31:22
fish---man---less

kill:

Enter indices of instances to kill, in a single line (e.g. 1, 01, 012). Here, fish with 9 threads is the process I would kill, so I enter 3.

If there are no more than 10 matches, a string of digits is a perfectly valid input. Otherwise, choices must be separated by commas or spaces: 1 2 12, 1,2,12, or any possible combination.

Install

npm install -g killsome

License

MIT