alias ps | grep

alias kfire='for i in `ps aux | grep [F]irefox `; do echo $i; kill $(($i)); done; '
This is an attempt to get a command which I can alias. It's ugly but it works. I'm hoping someone can suggest a cleaner version. I have tried.... # alias kfire="for i in $( ps aux | grep [F]irefox | awk \'{print $2}\' ); do kill $; done" # alias kfire=`kill $(ps aux | grep [F]irefox | awk '{print $2}' | tr '\n' ' ')` # alias kfire='ps au | grep -i [F]irefox | awk \'{ print $2 \'} ' and they all fail in a .bashrc I've tried escaping the quotes and can't find a way to make the single quotes ' that awk wants work. Maybe I'm just stubborn but I don't want to put in a little #!/bin/bash file just so I can kill a firefox process all in one stroke. This script works (it kills the process before it errors out)... it's just ugly and there may be a pretty way to do this.
Sample Output
$ kfire
-bash: 1.6: syntax error: invalid arithmetic operator (error token is ".6")

By: swerve
2010-12-27 01:47:58

These Might Interest You

What Others Think

pkill firefox or killall firefox Should work as well an much easier to use.
houghi · 390 weeks and 6 days ago
Careful using 'killall' - its not portable. Under Solaris, this will kill all processes, ignoring the argument.
ianh · 390 weeks and 6 days ago
^following that,if killall is not an option... here's a couple other options: alias kfire="kill $(pidof firefox)" alias kfire="kill $(ps aux | awk '/firefox/ {print $2}' | tr '\n' ' ')"
hdilemma · 390 weeks and 6 days ago
alias lssd='ps ax | grep -v grep | grep -i firefox | while read pid; do kill "${pid%% *}"; done' this command might be longer but it should handle multiple firefox process without the quoting.
ixseven · 390 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: