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



SSH connection with private key and port 222

Terminal - SSH connection with private key and port 222
ssh -i /root/.ssh/username\@hostname -p 222 [email protected]
2011-09-30 11:23:22
User: wallacetan
Functions: ssh
SSH connection with private key and port 222


There are 16 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

The command is correct, however, there is nothing to win on having a different private/public keypair for every different hosts, like it looks like here.

Having one for private, one at work, and one per script that cant use password is sufficient.

Comment by xeor 251 weeks and 3 days ago


Nonsense. I've generated a public/private key pair, and uploaded both to every Amazon instance for work. This is for file transfer between each instance, and between my terminal and the instance. While this is great, there is no way in hell I'm going to reuse the exact same key for my client's blog that I use for backup via rsync. That would give my client the keys to my employer's kingdom (and the reverse too).


Think about keying every single room in a hotel to the exact same biting. Super convenient, and what could possibly go wrong?

Comment by unixmonkey8121 251 weeks and 2 days ago

Your point of view

You must be signed in to comment.