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:



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





grep (or anything else) many files with multiprocessor power

Terminal - grep (or anything else) many files with multiprocessor power
find . -type f | parallel -j+0 grep -i foobar
2010-01-30 02:08:46
Functions: find grep
grep (or anything else) many files with multiprocessor power

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/


There is 1 alternative - vote for the best!

Terminal - Alternatives
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

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.

Know a better way?

If you can do better, submit your command here.

What others think

Have you done some tests to estimate the gain ?

I haven't a multiprocessor computer but I not totally convinced.

I think find command is more limited by disk rate than by cpu, but I could be wrong.

Comment by Kysic 296 weeks and 1 day ago

It is very dependent on file system whether it is faster. But if the files are cached (e.g. if you just searched for another string), then it is definitely faster.

Comment by unixmonkey10455 270 weeks and 5 days ago

Your point of view

You must be signed in to comment.