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.

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:



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!

Top Tags



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

Kill a bunch of processes with the same name

Terminal - Kill a bunch of processes with the same name
ps ax | grep <processname> | grep -v grep | awk '{print $1}' | sudo xargs kill -9
2009-03-24 19:52:47
User: copyhacker
Functions: awk grep kill ps sudo xargs
Kill a bunch of processes with the same name


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Perhaps a use of killall instead?

Comment by cde1985 418 weeks and 1 day ago

or pkill?

Comment by sander85 418 weeks and 1 day ago

and please don't use kill -9, this is very bad behaviour. Please try it with kill -15 and if it doesn't end the process kill -2. Then you can still use kill -9.

Comment by lme 418 weeks ago

Wow. grep piped to grep piped to awk. Never thought I'd see that.

Comment by atoponce 418 weeks ago

Apart from the fact that there's pkill and killall (depending on the OS), there are quite a lot of things that can be improved in this command line.

First, this is a nice trick to avoid the ugly "grep -v grep" part:

ps ax | grep '[p]rocessname'

Note that the first letter is enclosed in square brackets. This regular expression will match 'processname', but it will not match the grep command itself.

Second, it doesn't make sense to pipe from grep to awk because awk has a "built-in grep":

ps ax | awk '/[p]rocessname/{print $1}'
Comment by inof 408 weeks and 2 days ago

Your point of view

You must be signed in to comment.