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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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





kill some process (same as others) but parsing to a variable

Terminal - kill some process (same as others) but parsing to a variable
pkill -9 -f program
2009-07-12 14:46:14
User: ioggstream
kill some process (same as others) but parsing to a variable

Kills a process matching program. I suggest using

$ pgrep -fl program

to avoid over-killings

Nice the following: kills all bash process owned by guest

$ pkill -9 -f bash -u guest


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

Should use -9 as signal of last resort.

Kill -15 (the default if omitted) is the correct signal to send, failing that, try -1 and then possibly -11.

Reason being is -9 does not allow the process to do proper cleanup which can leave things in an inconsistent state, potentially causing data corruption.

Comment by Mehuge 332 weeks and 2 days ago

just to tell that you can specify signals..

nice explaination anyway ;)

Comment by ioggstream 332 weeks ago

Your point of view

You must be signed in to comment.