Hide

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.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

World cup college
Hide

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:

Hide

News

2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
2009-05-17 - Added duplicate suggestions to the new command form
When adding a new command, a quick background search is performed to make sure you're not duplicating a command already in the system.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Watch the progress of 'dd'

Terminal - Watch the progress of 'dd'
dd if=/dev/urandom of=file.img bs=4KB& pid=$!
2009-04-08 05:56:47
User: atoponce
Functions: dd
5
Up
Down
Watch the progress of 'dd'

Running this code will execute dd in the background, and you'll grab the process ID with '$!' and assign it to the 'pid' variable. Now, you can watch the progress with the following:

while true; do kill -USR1 $pid && sleep 1 && clear; done

The important thing to grasp here isn't the filename or location of your input or output, or even the block size for that matter, but the fact that you can keep an eye on 'dd' as it's running to see where you are at during its execution.

Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

Alternatively, if you have 'pv' installed:

pv /dev/urandom | dd of=file.img bs=4KB count=1234

This will display a progress bar for fixed-size input, or just a throughput speed for unlimited things like urandom.

Comment by flatcap 48 weeks and 3 days ago

dd if=/dev/urandom |cpipe -vt| dd of=file.img

Comment by oernii 48 weeks and 2 days ago

pv: http://ivarch.com/programs/pv.shtml

cpipe: http://cpipe.berlios.de/

(for the less observant) The trick here is that sending 'dd' the USR1 signal causes it to print the latest transfer statistics.

Comment by bwoodacre 48 weeks and 2 days ago

hey thx for reminding me to create alias of this

#ddp dd_args

function ddp() { dd "$@" & pid=$! && while true; do kill -USR1 $pid && sleep 1 && clear; done ;}
Comment by professoralex 43 weeks and 2 days ago

You could use

watch -n1 "kill -USR1 $pid"

instead of the sleep and clear in a for loop.

Comment by stuart 21 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts