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

Delete all files in current directory that have been modified less than 5 days ago.

Terminal - Delete all files in current directory that have been modified less than 5 days ago.
find ./ -mtime -5 | xargs rm -f
2009-03-23 21:00:45
User: skye
Functions: find rm xargs
Delete all files in current directory that have been modified less than 5 days ago.


There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Why use xargs?

find ./ -mtime -5 -exec rm '{}' \; works just fine.

Comment by ozymandias 402 weeks and 4 days ago

or why don't you use a rm -f `find ./ -mtime -5`?

Comment by jasvazquez 402 weeks and 4 days ago

jasvazquez, I think on some systems rm has an upper limit to the number of arguments it can handle at once. It is a *very* large number, but it exists.

Comment by ozymandias 402 weeks and 4 days ago

ozymandias - yes I ran into this on my Redhat 7.3 system where tons of error files were generated. You couldn't just rm * - it would say that there were too many files or something along those lines.

Comment by scifisamurai 402 weeks and 4 days ago

jasvazquez, the other reason your version won't work is because it doesn't quote each file properly. If there are special characters or spaces in any of those file names, it won't work.

I would modify ozymandias's slightly, and write it as:

find . -mtime 5 -exec rm {} +

The quotes are unnecssary around the braces, since they're not special characters in bash if there's nothing in between them.

Also, using +, instead of \; gives you a very slight performance boost, since it will run only one instance of rm for all the files (rm file1 file2 file3...), rather than one for each file (rm file1; rm file2; rm file3; ...), unless there are too many files to specify on the command line, then it will only run as many instances of rm as it absolutely has to (rm file1 file2 file3 ... ; rm file_bazillion file_bazillion1 file_bazillion2 ...).

Comment by goodevilgenius 402 weeks and 4 days ago

Sorry, that should have been -mtime -5

Comment by goodevilgenius 402 weeks and 4 days ago

@ozymandias xargs is highly efficient. Time it, and you'll see xargs scream, while -exec rm {} \; take its sweet time.

@jasvazquez http://www.commandlinefu.com/commands/view/1387/backticks-are-evil

Comment by atoponce 402 weeks and 4 days ago

The maximum number of shell arguments is usually at 4096. So you cannot delete more than ~4000 files with -exec rm {} \;

Comment by lme 402 weeks and 2 days ago

Your point of view

You must be signed in to comment.