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/
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.
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
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:
when ssh is running on a different port
There are 5 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
I assume people voted this down for obviousness. If ssh is running on another port, one will assume there's an option to give the port number and a quick man will reveal it.
What may not be so obvious, and may be useful to you if you frequently have to scp to a host listening on a non-standard port is you could add these two lines to your ~/.ssh/config file and then just use regular ssh/scp syntax:
Host <your-weird-port-host>Port 1837Note: I like to indent the lines under Host because they only apply to that host. The extra couple of spaces before Port got eaten by the site :-(