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.


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.

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

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

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
4
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 are 2 alternatives - vote for the best!

Terminal - Alternatives
pkill -9 -f program
2009-07-12 14:46:14
User: ioggstream
Tags: kill pgrep pkill
1

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

tokill=`ps -fea|grep process|awk '{ printf $2" "}'`; kill -9 $tokill;

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 291 weeks ago

most of it is not needed:

killall -9 PROCESS
Comment by ceesaxp 290 weeks and 6 days ago

pkill(1) can do this also.

Comment by cz8s 290 weeks and 4 days ago

killall by itself just works fine

killall firefox-bin
Comment by bwoodacre 271 weeks ago

We also use :

kill `ps -ef | grep irssi | grep -v grep | awk ?{print $2}?`
Comment by cafecoc85 119 weeks and 5 days 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 108 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts