Tag Info

New answers tagged

0

If the directory is part of the system or an installed package managed by rpm you can find out which package it is part of with rpm -qf /directory and then can try rpm -qV <package> (verify) to see what the installed permissions settings were. You can then revert to those with chmod manually or with rpm --setperms as stderr mentioned.


7

First off, chmod go-r doesn't remove write permissions, it removes read permissions. The contents of / is primarily directories; on directories read permission means you're allowed to list it. E.g., ls /bin will now give a permission denied (except for the directory owner and root, of course the owner is root in this case). If that was a typo and you meant ...


2

chmod go-r * doesn't affect special groups at all. It just affects the rights for the primary groups and the "others". The primary group for everything in / should be root. So that doesn't change anything at all as root can do whatever he wants anyway. The other accounts usually do not read the contents of the directories in / as they know their paths. ...


0

I am not sure, if I understand your question in its current form. If you don't care about a sub-directory with read access being placed in a directory without read access, then you can simply do: find . -type d -perm -u+r If you want to know, whether a specific user has read access to a directory, then get the group(s) she/he is a member of: groups ...


1

Maybe not an answer (as the post doesn't include enough information) but I can amend it if needed. When doing linux training courses I developed a way to quickly find the permission problem. I'm aware that you already performed some of the steps but I need to write it down in full for the sake of completeness. Switch to the user you want to use for access. ...


6

If you want to grant global write permission on that directory, you have to do chmod a+w wp.localhost [1] This is because omitting the 'who is affected' letter (u, g, o or a) implies a, but won't set bits that are set in your current umask. So, for example, if your umask was 0022, the 'write' bit is set in the 'group' and 'other' positions, and chmod ...


1

Perhaps an obvious question but... did you change also the permissions of files inside the directory? In other words, did you use the "-r" (recursive) flag when issuing the chown/chmod commands?



Top 50 recent answers are included