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

Change permissions of every directory in current directory

Terminal - Change permissions of every directory in current directory
find . -type d -exec chmod 755 {} \;
2009-06-07 08:17:06
User: marssi
Functions: chmod find
Change permissions of every directory in current directory

"find . -type d -print0 | xargs -0 chmod 755"

thanks masterofdisaster


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

find . -type d -exec chmod 755 {} +;

{} +: to let it behave like using xargs

the same command has been posted before

Comment by JesusSuperstar 411 weeks and 5 days ago


find . -type d -print0 | xargs -0 chmod 755

1. It is much faster of large amounts of files because chmod does not get invoked for every file seperately.

2. And besides null terminating the file name takes care of nasty spaces|quotes|your-favorite-non-printable-characters in file names.

3. Same goes for files:

find . -type f -print0 | xargs -0 chmod 644
Comment by masterofdisaster 411 weeks and 5 days ago

In zsh you can do the same with this command:

chmod 755 **/*(/)

It's fast, efficient and works with all filenames (spaces and anything).

To do the same with plain files:

chmod 644 **/*(.)

For those not familiar with zsh wildcards, this is how the above commands work: "**" is the same as "*", but it works recursively down the directory tree, so you don't have to use the find command. Any wildcard pattern can be followed by a set of flags in parentheses (there must be no space between!): "(/)" restricts the matches to directories only, and "(.)" does the same for plain files. There are many more wildcards and flags; this is just the tip of the iceberg.

Comment by inof 411 weeks and 5 days ago
find . -type d -print0 | xargs -0 chmod 755

+1; xargs is better

Comment by asmoore82 411 weeks and 4 days ago

Actually, koukos was right here -- using "{} +" in a find -exec command tells find to build the command with every matching file /before/ execution, so chmod would only be invoked once (unlike using "{} \;" which tells it to invoke the command once for every file matched)

I have a shared drive here in the office which I occasionally get permission problems with for other users, so I use

find . ! -perm /g=r -exec chmod g+r {} +

a lot: turns on the group readable bit for any files that don't currently have it on, in one invokation of chmod.

Comment by sanmiguel 411 weeks and 3 days ago

Beware, the ^above "zsh" method misses hidden files and folders. While there may be a way around this with zsh's options, why waste the time when `find` is Unix standard? Will zsh also search by perms or times? Will zsh combine search methods? Always pick the right tool for the job; `find` is for *finding*

Comment by asmoore82 411 weeks and 3 days ago
Comment by asmoore82 411 weeks and 3 days ago

^oops :/, excuse me :[

`xargs -0` is _still_ *better*; the "+" is *NOT* Portable.

Comment by asmoore82 411 weeks and 3 days ago

Your point of view

You must be signed in to comment.