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

One liner to check out CLOSE_WAIT and TIME_WAIT connection every five seconds while debugging network apps

Terminal - One liner to check out CLOSE_WAIT and TIME_WAIT connection every five seconds while debugging network apps
while true; do netstat -a|grep WAIT|wc -l; sleep 5; done
2013-06-19 09:19:41
User: adimania
Functions: grep netstat sleep wc
One liner to check out CLOSE_WAIT and TIME_WAIT connection every five seconds while debugging network apps

This has saved me many times while debugging timeout issues to "too many open files" issues. A high number of the order of thousand, indicates that somewhere connection is not being closed properly.


There are 4 alternatives - vote for the best!

Terminal - Alternatives
watch -n5 ss \| grep -c WAIT
2014-07-30 17:09:08
User: djpohly
Functions: grep watch
Tags: tcp ss iproute2

Uses the suggestions by jld on #12421 as well as the new iproute2 tools instead of old net-tools.

Know a better way?

If you can do better, submit your command here.

What others think


Share a website with you ,

( http://www.femalemalls.com/ )

Believe you will love it.

We accept any form of payment.


Comment by femalemalls7 174 weeks and 4 days ago

I suggest "netstat -an" so it won't do any DNS queries for faster calculation on a busy server.

while true; do netstat -an|grep WAIT|wc -l; sleep 5; done
Comment by nenominal 174 weeks and 1 day ago

- the construct "while true; do ...; sleep 5; done" can be replaced by the watch command

- "grep STRING | wc -l" can be replaced by "grep -c STRING"

So a more elegant version is:

watch --interval=5 netstat \| grep -c WAIT

Comment by jld 172 weeks and 1 day ago

Your point of view

You must be signed in to comment.