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:



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.

Top Tags



Kill a process by application

Terminal - Kill a process by application
kill -9 `pgrep $PROCESS_NAME`
2010-06-18 20:43:24
User: juanse006
Functions: kill
Kill a process by application

The pgrep retrieves the PID, then the KILL receive it, and kill it...

It works also if the application has more than one instance....


There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

voted down for the use of backticks. behold, the way of the Jedi:

kill -9 P(pgrep $PROCESS_NAME)
Comment by atoponce 249 weeks and 4 days ago

er, heh

kill -r $(pgrep $PROCESS_NAME)

a Jedi, i am not. nooooo.

Comment by atoponce 249 weeks and 4 days ago

and i give up. if only you could edit comments

Comment by atoponce 249 weeks and 4 days ago

atoponce: I don't think that's a good reason to vote this command down. By using backticks in the example, it also applies shells which do not support the newer style syntax. This isn't a bash or zsh only website. When available... sure, $() is a good habit... it makes complex substitutions much easier. But in this instance, there is no benefit to using one over the other.

Comment by recursiverse 249 weeks and 3 days ago

How about this. The same package that installs pgrep on most (all) distributions also installs pkill.

pkill -x $PROCESS_NAME pkill -9 -x $PROCESS_NAME
Comment by SuperJediWombat 248 weeks and 6 days ago

Note: Don't worry atoponce, I've got your back.

Comment by SuperJediWombat 248 weeks and 6 days ago

Your point of view

You must be signed in to comment.