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.

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





Maintained by Jon H.

Site originally by David Winterbottom (user root).

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Attach screen over ssh

Terminal - Attach screen over ssh
ssh -t remote_host screen -r
2009-07-23 06:15:04
User: recursiverse
Functions: screen ssh
Attach screen over ssh

Directly attach a remote screen session (saves a useless parent bash process)


There is 1 alternative - vote for the best!

Terminal - Alternatives
ssh -t user@some.domain.com /usr/bin/screen -xRR
2009-02-20 23:39:54
User: olifante
Functions: ssh

Long before tabbed terminals existed, people have been using Gnu screen to open many shells in a single text terminal. Combined with ssh, it gives you the ability to have many open shells with a single remote connection using the above options. If you detach with "Ctrl-a d" or if the ssh session is accidentally terminated, all processes running in your remote shells remain undisturbed, ready for you to reconnect. Other useful screen commands are "Ctrl-a c" (open new shell) and "Ctrl-a a" (alternate between shells). Read this quick reference for more screen commands: http://aperiodic.net/screen/quick_reference

Know a better way?

If you can do better, submit your command here.

What others think

Two things, the first, I would suggest -R instead of -r (so that if it cannot find an old session it just creates a new one.

ssh -t remote_host screen -R

And the second thing:

Why do we need the -t option?

Comment by Weboide 395 weeks and 4 days ago

-t forces a terminal to be allocated, otherwise ssh will assume you don't want one since you are only running a command and not opening a shell. Screen needs that terminal or else it won't find anything to attach to and exits.

Comment by recursiverse 395 weeks and 4 days ago

Thank you for this explanation.

Comment by Weboide 395 weeks ago

This can also be used with Byobu this way:

ssh -t remote_host byobu -R
Comment by Weboide 395 weeks ago

For that matter, use screen -RR if you figure to expect multiple screen sessions.

Comment by Buzzcp 377 weeks and 3 days ago

I prefere use RD reattach if possible with detach

ssh -t remote_host screen -RD
Comment by starchox 300 weeks and 3 days ago

Can someone explain how to create multiple sessions and run split screen for each session?

Comment by dtolj 196 weeks and 3 days ago

Your point of view

You must be signed in to comment.