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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



Periodically loop a command

Terminal - Periodically loop a command
while true; do ifconfig eth0 | grep "inet addr:"; sleep 60; done;
2009-04-01 19:29:28
User: bandit36
Functions: grep ifconfig sleep
Periodically loop a command

You can use this to loop any command to periodically see the output.

while true; do [YOUR COMMAND HERE]; sleep [# of seconds]; done;

Alternatively, you can put it in a simple shell script to save typing!


while true; do $1; sleep $2; done;

/path/to/script.sh "ifconfig eth0 | grep 'inet addr:'" 60


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

watch -n1 -d ifconfig eth0

Comment by bartman 315 weeks and 3 days ago

Watch equivalent:

watch -n60 'ifconfig eth0 | grep "inet addr:"'
Comment by SlimG 315 weeks and 3 days ago

Yeah, use watch, if it is available. The best part is that the -d option allows highlighting of the things that have changed since the last invocation. watch is part of the base ubuntu install and comes from the 'procps' package.

Comment by bwoodacre 315 weeks and 3 days ago

Alternatively, there's another really cool alternative to while: until, which negates the condition:

until false;do sleep 1;done

Which actually is handy for things like pinging a down machine

until ping -c1 machine;do sleep 1;done;beep

will make a beep when the machine is back up.

Comment by clockworkavian 315 weeks and 3 days ago

@SlimG- two things: 1) you don't need to nest the command. 2) if you insist on nesting it, for the love of everything good and holy, ditch the backticks.

Comment by atoponce 315 weeks and 3 days ago
while ifconfig eth0 | grep "inet addr:";do sleep 60; done;
Comment by lme 315 weeks and 3 days ago

@atoponce: 1) yes you do or grep won't fire until watch exits. 2) those aren't backticks, they're single quotes; quite different.

Comment by TheMightyBuzzard 315 weeks and 2 days ago

I used it to check my connection since I have some troubles with my ISP (yeah I know I could change...). I put time and date in a file every time my connection is down like this:

while true; do ping pong.sunet.se; date >> downTime; done;
Comment by unixmonkey3130 315 weeks and 2 days ago

Your point of view

You must be signed in to comment.