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



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

Share your terminal session real-time

Terminal - Share your terminal session real-time
mkfifo foo; script -f foo
2011-09-08 02:51:44
User: realist
Functions: mkfifo script
Share your terminal session real-time

One person does `mkfifo foo; script -f foo' and another can supervise real-time what is being done using `cat foo'.


There are 2 alternatives - vote for the best!

Terminal - Alternatives
tb send xmpp:[email protected]
2013-04-08 00:29:43

After installing Termbeamer (see termbeamer.com) you can use it to share a terminal session with one or more others even from behind a firewall or NAT.

Know a better way?

If you can do better, submit your command here.

What others think


I wasn't able to reproduce your commando on a RHEL 5.5. Can you please add more detailed instructions?



Comment by ztank1013 259 weeks ago

See also

screen -x

for a more advanced solution where all sharing persons can type in the session. (Although it needs elaborate setup to work with different users.)

Comment by hfs 258 weeks and 6 days ago

Nice thinking but not really working here on a CentOS 5.3 box.

Comment by DaveQB 258 weeks and 6 days ago

ztank, read the man pages for the 'script' command, and much will become clear. Essentially, script records all keystrokes, stdin and stdout, including timing information. The '-f' option allows you to specify a file where all of this information will be stored. Catting that file will send all of this back out to the screen, echoed at the same rate that the commands were typed in. You will have to make sure that script is installed on your box for this command to work.

To test this:

in one terminal,

mkfifo foo

in a second terminal

cat foo

in the first terminal

script -f foo

Then run several commands in the first terminal, and they will be echoed in both terminal 1 and terminal 2.

Comment by bartonski 258 weeks and 1 day ago

if you want to keep a transcript of the session, you can simply run

script -f asdf

then have observers run

tail -f asdf

(In this case asdf is *not* a fifo)

For some reason, there is a slight delay between typing and seeing text echo under 'tail -f asdf' (whereas I saw no delay when catting the fifo 'foo').

Comment by bartonski 258 weeks ago

Your point of view

You must be signed in to comment.