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/
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.
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
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:
This is useful for command line 'recycle bins' and such like
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
You could get the "arg list too long error".
Use this instead:
find -maxdepth 1 -mindepth 1 -mtime +7 -exec rm -f {} +or
find -maxdepth 1 -mindepth 1 -mtime +7 | xargs rm -fQuite true. Though this has never happened to me with bash on linux (only sh on windows). Also you'd need to have an awful lot of files in the top level of your tree...
Oooo, dangerous. Never use "rm -rf" on unescaped command lines. If there's (ugh) spaces in filenames, catastrophic things can happen. A filename with a period surrounded by space ("foo .") deletes everything under the current directory. A filename with a tilde separated by spaces ("foo ~") nukes your home directory.
Well, the tilde example doesn't delete the home directory in _this_ case (as the tilde isn't expanded), but there are other combinations where it could happen. In fact, for this kind of use it's better to use tmpreaper(1). It is meant for this kind of use, and it checks the access time instead of the file modification time. Because a file isn't modified in a week or so, doesn't mean it isn't used by processes in a read-only way.
Forget about expansion, just use find's delete capability:
find -mtime +7 -delete@bwoodacre: does that delete dirs? and does it force delete (-f)?
About the "arg list too long error" :
http://www.in-ulm.de/~mascheck/various/argmax/
it is quite safe since linux 2.6.23 as the arg list is valid till it doesn't fill the quarter of the stack.