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:



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.

Top Tags





Move files older than 30 days in current folder to

Terminal - Move files older than 30 days in current folder to
find . -mtime +30 -exec mv {} old/ \;
2014-02-09 23:05:41
User: minnmass
Functions: find mv
Move files older than 30 days in current folder to

Use find's built-in "exec" option to avoid having to do any weirdness with quoting.


There are 27 alternatives - vote for the best!

Terminal - Alternatives
for i in $(find . -mtime +30); do mv $i old/; done
2014-02-05 01:24:45
User: valferon
Functions: find mv
Tags: bash file

Will move in that case every file in the current folder older than 30 days to the "old" folder

Replace "mv $i old/" by any command such as rm / echo to do something different.

Know a better way?

If you can do better, submit your command here.

What others think

Useful, but there's a few problems with the command as it is.

The 'old' directory can't be a subdirectory of the current directory, or find will get upset.

The command doesn't do the right thing with directories, so you need to add "-type f" to find.

Also, if you have any duplicate filenames they'll get trampled, so you might want to change mv to

mv --backup=numbered
Comment by flatcap 64 weeks and 2 days ago

i eschew : find ... -exec stuff , preferring file ... | xargs stuff

why? have you ever counted the questions from people wondering why the -exec didn't work? "i didn't see my '..' files". duh? why not first run the find and inspect the files you'll see. so for this sort of thing:

$ find . -mtime +30 -type f | cpio -pdluvm $(needir ../old)| xargs rm -f


$ needir () { [[ -d $1 ]] || mkdir -p $1; echo $1; }

Comment by applemcg 62 weeks and 4 days ago

Your point of view

You must be signed in to comment.