39

How do I recursively execute chmod or chown for hidden files?

sudo chmod -R 775 * does not work on hidden files.

The same thing goes for sudo chown -R user:group.

4 Answers 4

44

If you're okay also chmod'ing the current directory, do that and let -R do the heavy lifting. -R does not ignore hidden files.

sudo chmod -R 775 .
3
  • 14
    This (* .*) is not the safest way to do it. Particularly, it would recurse into parent directory, which means it chmods also siblings of the current directory. The proper way would be * ..?* .[^.]* or, even better (considering the wildcards might not match any files) $(ls -A).
    – jpalecek
    Oct 12, 2011 at 13:34
  • 1
    @jpalecek: The output of ls is unparseable; trying to parse it is asking for trouble. The proper approach is to use shell globbing. Dec 11, 2011 at 17:58
  • Even though in linux you have the ability to change the order of args for chmod, when doing x-plat scripts between linux and OS X, this is the order you should use, e.g., sudo chmod 775 -R would go belly-up, so stick to this answer. Jun 17, 2016 at 18:30
40

* doesn't include hidden files by default, but if you're in bash, you can do this with:

shopt -s dotglob

Read more about it in bash's builtin manual:

If set, Bash includes filenames beginning with a `.' in the results of filename expansion.

This will make * include hidden files too.

chmod -R 775 *

Disable it with:

shopt -u dotglob
2
  • 2
    How to do that in zsh ? Oct 25, 2014 at 13:57
  • 2
    You use the (D) globbing qualifier, e.g. chmod -R 775 *(D)
    – slhck
    Oct 25, 2014 at 14:39
3

All files in the current directory, recursively, including hidden files:

chmod 755 -R ./* ./.[!.]*

All files in the current directory, not recursively, including hidden files:

chmod 755 ./* ./.[!.]*

This will not change an exception filename starting with 2 dots, as example, "./..thisonescapesunharmed.txt"

Also, be carefull not to remove the "x" bit, or else all your directories will not be accessible (one needs the x bit to cd into a dir).

Remember this alert: never use bare * but ./* instead.

To avoid problems setting permissions on directories, use find instead.

find . -type f -exec chmod `VALUE` {} \;
2

Another option is to use find i like it since you can have very fine grained control over it.

find <path to start from> -exec chown <options> {} \+

find -path '<path to include>' -exec chown <options> {} \+

The only downside is that find has different syntax on different versions.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .