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

Listing directory content of a directory with a lot of entries

Terminal - Listing directory content of a directory with a lot of entries
perl -le 'opendir DIR, "." or die; print while $_ = readdir DIR; closedir DIR'
2011-04-04 06:21:39
User: bierik
Functions: perl
Listing directory content of a directory with a lot of entries

Ever wanted to get the directory content with 'ls' or 'find' and had to wait minutes until something was printed? Perl to the rescue. The one-liner above(redirected to a file) took less than five seconds to run in a directory with more man 2 million files. One can adapt it to e.g. delete files that match a certain pattern.


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


Comment by bashrc 320 weeks and 5 days ago

What options to use with find? I tried it in the same directory and it took almost two minutes. The perl solution took less than five seconds.

Comment by bierik 320 weeks and 5 days ago

Are you voting this command down because you personally don't like it? Or is it because it does not work? Because it worked fine for me, and it took seconds to complete.

Comment by SuperFly 320 weeks and 5 days ago

The problem has to do with buffering, I think. Perl handles this differently than `ls`, but that's probably because Perl adds another layer of buffering. If that's indeed the case, `find` may not solve this issue. Anyone who actually knows what they're talking about?

Comment by kaedenn 320 weeks and 4 days ago

Looking at the straces of perl and find, I see that find calls newfstatat for every single file it finds, blowing up the strace output file to about 200MB. Perl doesn't call newfstatat at all and its strace file is less than one MB. Why is this system call made? Can one suppress it?

Comment by bierik 320 weeks and 4 days ago

Your point of view

You must be signed in to comment.