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 any lingering ssh processes

Terminal - Kill any lingering ssh processes
for i in `ps aux | grep ssh | grep -v grep | awk {'print $2'}` ; do kill $i; done
2009-02-21 02:07:22
User: jcwaters
Functions: awk grep kill ssh
Kill any lingering ssh processes


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Sweet, now my mysql backup script is complete bwahahaha! (I can make sure that pesky mysqld is really stopped before tarring /var/lib/mysql) init.d has failed me before) thanks!

Comment by foucault 321 weeks and 2 days ago

You do not need a loop for that

ps aux | grep ssh | grep -v grep | awk {'print $2'} | kill -9

or better

ps aux | grep ssh | grep -v grep | awk {'print $2'} | xargs -r kill -9
Comment by lux 321 weeks and 2 days ago


killall ssh
Comment by novas0x2a 321 weeks and 2 days ago

killall is sweet, just what I need, thanks nova.

Comment by foucault 321 weeks and 2 days ago

If you do this while ssh'ed in, you'll probably kill your own session...

Comment by sud0er 321 weeks and 1 day ago

Well, you might use ps -A and check whether it is in your terminal (checking for pts/0, etc) and do it that way. But that works.

Comment by farglenargle 320 weeks and 5 days ago

Your point of view

You must be signed in to comment.