4 ms·

You mean `ps aux | grep` which I am also guilty of using every time ? You might be interested in pgrep (http://linux.die.net/man/1/pgrep http://linux.die.net/ma

by rakoo 10y ago

You mean `ps aux | grep` which I am also guilty of using every time ? You might be interested in pgrep (http://linux.die.net/man/1/pgrep http://linux.die.net/man/1/pgrep) as well.

semi-extrinsic 10y ago
For interactive use, I strongly recommend htop if you're still doing stuff like "ps aux | grep" and then "kill 84728". Htop is top on steroids: ncurses-based and very fast, has colors, threaded or flat process view, sorting by different criteria like cpu or ram use, searching for substring match in process name, interface to killing/signalling to selected process, etc. http://hisham.hm/htop/ http://hisham.hm/htop/
- johnchristopher 10y ago
  I am more a `killall <processname>` guy.
  - koolba 10y ago
    > I am more a `killall <processname>` guy. I've made a note to name the executable for my next daemon "humans".
  - Rondom 10y ago
    Don't do that on Solaris ;-)
    - joosters 10y ago
      Been there, done that :( See also the 'reboot' (or is it the 'poweroff' ?) command, which is much more direct than the Linux equivalent...
  - amyjess 10y ago
    Sometimes, I want something a little more murderous, so I tend to write this script on most systems I use: ps -ef | grep $1 | awk '{print "kill -9 " $2}' | sh Usually stored as /usr/local/bin/kll I've found it's very useful for killing specific Java programs without having to killall -9 java. (and, yeah, I should probably be using ps -efww instead of ps -ef, but old habits die hard... I've already got ps aliased to ps -ww for interactive use, so I should probably change this script...)
    - imtringued 10y ago
      You should try jps it's similar to ps but only lists java processes with their real names instead of just "java". It's included in pretty much every JDK.
  - ozzmotik 10y ago
    oh god i thought I was the only one
  - voidz 10y ago
    'pkill' can do a bit more, it's the better alternative in my opinion.
- mxuribe 10y ago
  Agreed, htop is pretty awesome!
- amyjess 10y ago
  I discovered htop when regular top changed its default behavior to be nigh unusable. htop was recommended as an alternative, and while I've since learned how to configure top to go back to its old behavior [0], I've found that I just prefer htop now. [0] https://bbs.archlinux.org/viewtopic.php?id=189757 https://bbs.archlinux.org/viewtopic.php?id=189757
- emidln 10y ago
  For just viewing system information, I usually prefer glances to htop, although it can't signal. It has a curses interface and also includes network traffic, docker containers, disk IO, and it's nicely pluggable for both output formats (it can dump to CSV at interval as a daemon or while you're running it interactively (or something like graphite/influxdb if you have those)) as well as collection mechanisms (you write some python).

by rakoo 10y ago

You mean `ps aux | grep` which I am also guilty of using every time ? You might be interested in pgrep (http://linux.die.net/man/1/pgrep http://linux.die.net/man/1/pgrep) as well.

semi-extrinsic 10y ago

For interactive use, I strongly recommend htop if you're still doing stuff like "ps aux | grep" and then "kill 84728". Htop is top on steroids: ncurses-based and very fast, has colors, threaded or flat process view, sorting by different criteria like cpu or ram use, searching for substring match in process name, interface to killing/signalling to selected process, etc. http://hisham.hm/htop/ http://hisham.hm/htop/

johnchristopher 10y ago
I am more a `killall <processname>` guy.
- koolba 10y ago
  > I am more a `killall <processname>` guy. I've made a note to name the executable for my next daemon "humans".
- Rondom 10y ago
  Don't do that on Solaris ;-)
  - joosters 10y ago
    Been there, done that :( See also the 'reboot' (or is it the 'poweroff' ?) command, which is much more direct than the Linux equivalent...
- amyjess 10y ago
  Sometimes, I want something a little more murderous, so I tend to write this script on most systems I use: ps -ef | grep $1 | awk '{print "kill -9 " $2}' | sh Usually stored as /usr/local/bin/kll I've found it's very useful for killing specific Java programs without having to killall -9 java. (and, yeah, I should probably be using ps -efww instead of ps -ef, but old habits die hard... I've already got ps aliased to ps -ww for interactive use, so I should probably change this script...)
  - imtringued 10y ago
    You should try jps it's similar to ps but only lists java processes with their real names instead of just "java". It's included in pretty much every JDK.
- ozzmotik 10y ago
  oh god i thought I was the only one
- voidz 10y ago
  'pkill' can do a bit more, it's the better alternative in my opinion.
mxuribe 10y ago
Agreed, htop is pretty awesome!
amyjess 10y ago
I discovered htop when regular top changed its default behavior to be nigh unusable. htop was recommended as an alternative, and while I've since learned how to configure top to go back to its old behavior [0], I've found that I just prefer htop now. [0] https://bbs.archlinux.org/viewtopic.php?id=189757 https://bbs.archlinux.org/viewtopic.php?id=189757
emidln 10y ago
For just viewing system information, I usually prefer glances to htop, although it can't signal. It has a curses interface and also includes network traffic, docker containers, disk IO, and it's nicely pluggable for both output formats (it can dump to CSV at interval as a daemon or while you're running it interactively (or something like graphite/influxdb if you have those)) as well as collection mechanisms (you write some python).