Timeline for Force new files to inherit specified ownership and permissions
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 30, 2017 at 3:05 | history | suggested | htoip | CC BY-SA 3.0 |
Use descriptive title, improve English, remove linux tag
|
| Mar 30, 2017 at 2:32 | review | Suggested edits | |||
| S Mar 30, 2017 at 3:05 | |||||
| Feb 16, 2017 at 13:29 | answer | added | dr_ | timeline score: 1 | |
| Feb 16, 2017 at 12:29 | answer | added | ceving | timeline score: 1 | |
| Feb 16, 2017 at 10:36 | comment | added | ConfusedClown | By this, will not the user 'prateekkaien' gain access of rwx as of the group ? The superuser is the administrator. It can create and modify files but the user can only view/read it. I didnt get what it says above | |
| Feb 16, 2017 at 10:27 | comment | added | dirkt |
As a further example, you normally just make groups according to the necessary roles, and then assign users to it. For example, my /usr/local as a setgid of staff, and I'm member of staff, so I can work with files below /usr/local any way I want. If some other user who is also a member of staff does the same, I don't care, because as a member of the same group, I can modify his files etc.
|
|
| Feb 16, 2017 at 10:21 | comment | added | Murphy |
You could swap user and group to achieve this: Create a group prateekkaien (or use an existing one), use setgid as described by @dirkt, set the permissions accordingly and leave the user untouched.
|
|
| Feb 16, 2017 at 10:19 | history | edited | ConfusedClown | CC BY-SA 3.0 |
added 138 characters in body
|
| Feb 16, 2017 at 10:17 | comment | added | ConfusedClown | I want the user to be able to read/view the file. When a file is being created it is being user-owned by 'superadmin' with permission rwx Basically all I want is, the files to inherit the same user and groups and same permissions and ownerships as of the parent directory | |
| Feb 16, 2017 at 10:08 | comment | added | dirkt | You can force the group ownership with the setgid bit on directories, but it works only for the group, not for the user. So the question becomes: why do you want to change user ownership, too, and what do you hope to achieve by that? | |
| Feb 16, 2017 at 10:01 | history | asked | ConfusedClown | CC BY-SA 3.0 |