Ubuntu – Permisions set to unknown after chmod 777

chmodpermissions

I just noticed that after running

chmod 777 *

on a directory that has sub-directories in it does what you would expect. It sets the permissions of everything, including the sub-directories to 777. However, if you then decided that you didn't want to do that, and run

chmod 644 *

Now the contents of the sub-directories get set unknown permissions and you cannot change them back.

Why does that happen? Is this the expected behavior, or a bug? Is there a way to restore the file permissions?

Since the files I had were in a zip file in another location, I just deleted the entire directory, and unzipped the zip file again, but I would like to know the causes of this "problem", and it's remedies.

Some additional info, I am running those command on a remote machine over SSH.

Best Answer

Probably best to use find for this sort of thing.

Directories need to be x access , files do not, so different set of permissions.

# Files
find . -type f -exec chmod 644 '{}' \;

# Directories
find . -type d -exec chmod 755 '{}' \;

Related Solutions

Ubuntu – Permissions for apache webroot folder on dev server

I am working on a related issue, but in your case, you could just add yourself to the web group

sudo adduser $USER www-data

replace USER$ with your username of course. www-data is the group used for apache web access.

Ubuntu – Why does chmod 644 make directories inaccessible

As noted in the manpage for chmod with relation to permissions:

The letters rwxXst select file mode bits for the affected users: read (r), write (w), execute (or search for directories) (x), execute/search only if the file is a directory or already has execute permission for some user (X)

The executable bit on a folder is explained above as a 'search' permission; i.e. the execute bit merely allows you to access the folder in a file browser or to move to the folder from the terminal by running the cd command or running ls ~/folder to list the files in the folder.

The folder must be executable for the owner, although the superuser would still be able to access the folder as when using sudo any file or directory can be accessed or deleted. In addition, directory and file permissions are explained further in this useful article at Stackoverflow.

It is also important to note that 'executing' the folder doesn't mean you are actually running any code or commands like when a executable binary or script is run.

For a home Desktop user (though perhaps not for your server) most folders within $HOME have the execute permission set for user, group, and other if viewed with stat ~/myfolder (excerpt below):

Access: (0755/drwxr-xr-x)  Uid: ( 1000/    mike)   Gid: ( 1000/    mike)

The standard permissions for folders within $HOME are 755 or 775 and for files they are 644. However, the rest of the filesystem will differ. Again, folders must have the execute bit for the owner or they will not be able to be opened by him. It is important to be careful with chmod when changing permissions and particularly when doing it recursively as the situation can quickly get messed up.

For more information, see man chmod or the Ubuntu manpages online, and this article at Superuser.

Best Answer

Related Solutions

Ubuntu – Permissions for apache webroot folder on dev server

Ubuntu – Why does chmod 644 make directories inaccessible

Related Question