Ever come across the problem of needing to chmod a directory and its many, many, sub-directories, but you don\u2019t want to touch any of the files? Maybe it\u2019s the exact opposite, or you need to recursively change the permissions on only files with a specific extension. Well I had a similar problem with my web server settings.<\/p>\n
find . -type d -exec chmod 755 {} \\;<\/pre>\nfind<\/code>\u201d all directories, starting at \u201c.<\/code>\u201c, and chmod them to\u00a0755<\/code>.<\/li>\n<\/ul>\nfind . -type f -exec chmod 644 {} \\;<\/code><\/pre>\n\n- This snippet does the opposite and finds only files. The difference (beside the file permissions) is the \u201c
-type f<\/code>\u201c, \u201cf<\/code>\u201d specifies files and \u201cd<\/code>\u201d directories.<\/li>\n<\/ul>\nIf you check the comments, you\u2019ll find a few additional snippets:<\/p>\n
find . -type f -name '*.htm*' -exec chmod 644 {} \\;<\/code><\/pre>\n\n- This lets you \u201c
find<\/code>\u201d files (\u201c-type f<\/code>\u201c) with a specific extension (\u201c-name '*.htm*'<\/code>\u201c) and chmod them with your desired permission (\u201c-exec chmod 644 {}<\/code>\u201c).<\/li>\n<\/ul>\nchmod -R o+rX<\/code><\/pre>\n\n- This snippet will recursively chmod \u201cother\u201d (\u201c
o<\/code>\u201c) permissions with read\/eXecutable (\u201c+rX<\/code>\u201c), and the capital X ensures that directories and files set (user\/group permissions) to executable will be properly modified, while ignoring regular (non-executable) files.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"Ever come across the problem of needing to chmod a directory and its many, many, sub-directories, but you don\u2019t want to touch any of the files? Maybe it\u2019s the exact opposite, or you need to recursively change the permissions on … Continue reading