Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.


Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.
Hide

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:

Hide

News

May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!
Hide

Top Tags

Hide

Functions

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

ps -ef | grep PROCESS | grep -v grep | awk '{print $2}' | xargs kill -9

Terminal - ps -ef | grep PROCESS | grep -v grep | awk '{print $2}' | xargs kill -9
ps -ef | grep PROCESS | grep -v grep | awk '{print $2}' | xargs kill -9
2009-02-21 15:55:38
User: f4nt
Functions: awk grep kill ps xargs
7
ps -ef | grep PROCESS | grep -v grep | awk '{print $2}' | xargs kill -9

kills all pids matching the search term of "PROCESS". Be careful what you wish for :)

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
tokill=`ps -fea|grep process|awk '{ printf $2" "}'`; kill -9 $tokill;
ps -ef | grep PROCESS | grep -v grep | awk '{system "kill -9" $2}

Know a better way?

If you can do better, submit your command here.

What others think

grep is not needed

ps -ef | awk '/PROCESS/ && !/awk/ {print $2}' | xargs -r kill -9
Comment by lux 392 weeks and 3 days ago

most of it is not needed:

killall -9 PROCESS
Comment by ceesaxp 392 weeks and 2 days ago

pkill(1) can do this also.

Comment by cz8s 392 weeks ago

killall by itself just works fine

killall firefox-bin
Comment by bwoodacre 372 weeks and 3 days ago

We also use :

kill `ps -ef | grep irssi | grep -v grep | awk ?{print $2}?`
Comment by cafecoc85 221 weeks and 1 day ago

The grep might be needed in some cases. For example i want to find a specific java routine with some parameters and kill only that.

Can't just go on killing all java processes, could kill some glassfish or tomcat processes on one command..

Comment by cabaro 209 weeks and 3 days ago

Your point of view

You must be signed in to comment.