Hide

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.

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Optimal way of deleting huge numbers of files

Terminal - Optimal way of deleting huge numbers of files
find /path/to/dir -type f -delete
2009-12-09 01:30:52
User: SlimG
Functions: find
9
Optimal way of deleting huge numbers of files

Optimal way of deleting huge numbers of files

Using -delete is faster than:

find /path/to/dir -type f -print0 | xargs -0 rm find /path/to/dir -type f -exec rm {} + find /path/to/dir -type f -exec rm \-f {} \;

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
find /path/to/dir -type f -print0 | xargs -0 rm
2009-01-26 11:30:47
User: root
Functions: find xargs
12

Using xargs is better than:

find /path/to/dir -type f -exec rm \-f {} \;

as the -exec switch uses a separate process for each remove. xargs splits the streamed files into more managable subsets so less processes are required.

find /path/to/dir/ -type f -exec rm {} +

Know a better way?

If you can do better, submit your command here.

What others think

What is non-optimal about

cd /path/to/dir; rm -rf ./*

? If you don't want --force, leave off the -f.

Comment by bwoodacre 259 weeks and 2 days ago

It's slower

Comment by SlimG 259 weeks and 2 days ago
cd /path/to/dir; rm ./*

is the same as:

rm /path/to/dir/*

and has the same drawback: it will fail with "too many arguments" if there is a very large number of files.

=====================

The -delete option to find is non-standard.

Comment by cfajohnson 259 weeks and 2 days ago

The "very large number of files" problem is easily avoided with

cd /path/to/dir/.. ; rm -rf dir

certainly the shell-expansion thing could be avoided by calling rm like this, but why is find faster? Is it skipping checks that rm does?

Comment by bwoodacre 259 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts