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





Shell recorder with replay

Terminal - Shell recorder with replay
script -t /tmp/mylog.out 2>/tmp/mylog.time; <do your work>; <CTRL-D>; scriptreplay /tmp/mylog.time /tmp/mylog.out
2011-01-19 07:16:30
User: olorin
Functions: script
Shell recorder with replay

If you provide the option -t to the script command and redirect stderr into a file, the timing information on what is going on on the terminal, is also stored.

You can replay the session via the scriptreplay command, where you can also provide a speedup factor (see the man page for details).

Great for demonstration purposes ...


There are 2 alternatives - vote for the best!

Terminal - Alternatives
script -t 2> timing.txt -a session.txt ; Run some commands here; exit; scriptreplay timing.txt session.txt

Know a better way?

If you can do better, submit your command here.

What others think

Where does scriptreplay come from?

Comment by DaveQB 245 weeks and 5 days ago

It's part of the util-linux package

Comment by olorin 245 weeks and 5 days ago

Not on CentOS 5

david.ward@om012234 ~ $ rpm -ql util-linux |grep reply david.ward@om012234 ~ $ rpm -qa util-linux util-linux-2.13-0.50.el5.x86_64 david.ward@om012234 ~ $ rpm -ql util-linux |grep reply
Comment by DaveQB 245 weeks and 4 days ago

Tried to grep for replay instead of reply?

Comment by olorin 245 weeks and 4 days ago

Oh oops. But yes.

david.ward@om012234 ~ $ rpm -ql util-linux |grep replay david.ward@om012234 ~ $
Comment by DaveQB 245 weeks ago

> cat /etc/SuSE-release

SUSE Linux Enterprise Server 11 (x86_64)



> rpm -ql util-linux |grep replay



Ok, you win :D. So maybe this is SuSE specific.

Comment by olorin 245 weeks ago

Haha. Maybe it (scriptreplay) should be on all distros. Sound great.

Comment by DaveQB 244 weeks and 5 days ago

Your point of view

You must be signed in to comment.