Change permissions of every directory in current directory

find . -type d -exec chmod 755 {} \;
"find . -type d -print0 | xargs -0 chmod 755" thanks masterofdisaster

By: marssi
2009-06-07 08:17:06

What Others Think

find . -type d -exec chmod 755 {} +; {} +: to let it behave like using xargs the same command has been posted before
JesusSuperstar · 634 weeks and 1 day ago
Try: 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
masterofdisaster · 634 weeks and 1 day 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.
inof · 634 weeks ago
find . -type d -print0 | xargs -0 chmod 755 +1; xargs is better
asmoore82 · 633 weeks and 6 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.
sanmiguel · 633 weeks and 6 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*
asmoore82 · 633 weeks and 6 days ago
asmoore82 · 633 weeks and 6 days ago
^oops :/, excuse me :[ `xargs -0` is _still_ *better*; the "+" is *NOT* Portable.
asmoore82 · 633 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

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.


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: