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 some pids without specific pid

Terminal - kill some pids without specific pid
kill -9 `ps aux | grep "search_criteria" | awk '{if ($2 != pid) print $2}'`
2010-09-16 08:52:59
User: ozgurkuru
Functions: awk grep kill
kill some pids without specific pid

search_criteria = what do you want to kill

pid = pid of you dont kill


There is 1 alternative - vote for the best!

Terminal - Alternatives
pkill -9 search_criteria
2010-09-16 10:02:25
User: hadace

pgrep, pkill - look up or signal processes based on name and other attributes

Know a better way?

If you can do better, submit your command here.

What others think

pkill -9 search_criteria not same with my command.

my command kill some jobs in same job groups. for example,

you have this scripts,




And you run all of this scripts. And you want to kill backup_A.py and backup_C.py


you put backup_B.py's pid to this command... such us:

kill -9 `ps aux | grep "var/scripts" | awk '{if ($2 != backup_B.py's_pid) print $2}'`

Comment by ozgurkuru 348 weeks and 4 days ago

Of course it's overcomplicated and in most cases pgrep or killall is what you need. BTW grep is not needed here, awk can do its job

kill -9 `ps aux | awk '/search_criteria/{if ($2 != pid) print $2}'`

Comment by zolden 348 weeks and 4 days ago

@zolden thanks for update.

Comment by ozgurkuru 348 weeks and 4 days ago

Your point of view

You must be signed in to comment.