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

List 10 largest directories in current directory

Terminal - List 10 largest directories in current directory
du -hs */ | sort -hr | head
2010-11-28 15:08:01
User: eronisko
Functions: du sort
List 10 largest directories in current directory

Directories listed in human-readable format


There are 2 alternatives - vote for the best!

Terminal - Alternatives
du -hsx * | sort -rh | head -10
du . -mak|sort -n|tail -10
2010-12-03 19:28:55
User: georgesdev
Functions: du sort tail

du -m option to not go across mounts (you usually want to run that command to find what to destroy in that partition)

-a option to also list . files

-k to display in kilobytes

sort -n to sort in numerical order, biggest files last

tail -10 to only display biggest 10

Know a better way?

If you can do better, submit your command here.

What others think

Unfortunately my "sort" doesn't support the -h parameter, so I'd need to remove the "-h" from both "du" and "sort", like this:

du -s */|sort -r|head

If you really want sizes that look like "1K" instead of "1024", and you can live with *two* passes of the "du" command, then this alternative works for me:

du -sh $(du -s */|sort -r|head|cut -f2-)

For what it's worth, I prefer to use just "*" instead of "*/", because 1) symlinks might be in the pwd and I typically don't care about the sizes of those, and 2) if there's a large file in the pwd I usually want to know about it. Also, I prefer to have the largest directories near the bottom of the output. Thus the command that I usually use is a minor variant of this:

du -sh $(du -s *|sort|tail|cut -f2-)

The actual command I use has some features for error-checking and passing in overrides of "*", but it's the same basic idea. Someday I'd like to eliminate the second pass of "du", but so far it hasn't been enough of a problem to bother fixing it.

Comment by willdye 330 weeks ago

Your point of view

You must be signed in to comment.