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

grep (or anything else) many files with multiprocessor power

Terminal - grep (or anything else) many files with multiprocessor power
find . -type f -print0 | xargs -0 -P 4 -n 40 grep -i foobar
2009-08-05 23:18:44
User: ketil
Functions: find grep xargs
grep (or anything else) many files with multiprocessor power

xargs -P N spawns up to N worker processes. -n 40 means each grep command gets up to 40 file names each on the command line.


There is 1 alternative - vote for the best!

Terminal - Alternatives
find . -type f | parallel -j+0 grep -i foobar
2010-01-30 02:08:46
Functions: find grep

Parallel does not suffer from the risk of mixing of output that xargs suffers from. -j+0 will run as many jobs in parallel as you have cores.

With parallel you only need -0 (and -print0) if your filenames contain a '\n'.

Parallel is from https://savannah.nongnu.org/projects/parallel/

Know a better way?

If you can do better, submit your command here.

What others think

Since grep is mostly IO-bound, I doubt it will benefit much from running in parallel.

Comment by spatz 403 weeks and 3 days ago

I don't see how the "-n 40" is needed nor relevant. Any clarification on why you use that?

Comment by linuxrawkstar 403 weeks and 2 days ago

the xargs man page *specifically* recommends using the -n with -P, and explains why...

Comment by eichin 402 weeks and 3 days ago

The xargs version risks lines being mixed:

Assume you have two files with matching lines that are grepped by each their process and that these lines are long. You then have a race condition with a risk of getting a mixed output like this:

start_of_line_from_file1 line_from_file2

end_of_line_from file1

The Parallel version does not suffer from this.

Comment by unixmonkey8046 378 weeks and 1 day ago

Yes, I guess the output could be interleaved in some cases (perhaps lines longer than BUFSIZ). It seems parallel does some input/output trickery to avoid this. It can also force output order to be the same as the input order, despite tasks finishing out of order.

But this is only an issue if the result of the executed program is output to stdout. If your program writes somewhere else, or does something else entirely, xargs (which is probably more common) does the trick.

Comment by ketil 377 weeks and 3 days ago

Your point of view

You must be signed in to comment.