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:
One person does `mkfifo foo; script -f foo' and another can supervise real-time what is being done using `cat foo'.
There are 7 alternatives - vote for the best!
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.
If you can do better, submit your command here.
You must be signed in to comment.
Hi,
I wasn't able to reproduce your commando on a RHEL 5.5. Can you please add more detailed instructions?
Thanks,
ztank
See also
screen -xfor a more advanced solution where all sharing persons can type in the session. (Although it needs elaborate setup to work with different users.)
Nice thinking but not really working here on a CentOS 5.3 box.
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 fooin a second terminal
cat fooin the first terminal
script -f fooThen run several commands in the first terminal, and they will be echoed in both terminal 1 and terminal 2.
if you want to keep a transcript of the session, you can simply run
script -f asdfthen 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').