Timeline for Prevent directory permission change (or cronjob to work around)
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2012 at 19:45 | vote | accept | TecBrat | ||
| Aug 10, 2012 at 17:50 | history | edited | TecBrat | CC BY-SA 3.0 | added 727 characters in body; edited title |
| Aug 10, 2012 at 0:24 | vote | accept | TecBrat | ||
| Aug 10, 2012 at 18:07 | |||||
| Aug 9, 2012 at 21:17 | answer | added | Richard Hum | timeline score: 0 | |
| Aug 8, 2012 at 6:18 | comment | added | tacotuesday | Run ls -Z on the directory and post the output. This will give you permissions, ownership, and SELinux details. You may be able to set something up using SELinux to do what you're thinking. Also, you could change the user ownership to your user, create a group to put the other users in, and change the group ownership to that group. Then modify the permissions for the group accordingly. Scripts that run as root, though, will still have full access unless set under a restricted SELinux property or chmodding it to 000 like they've already done, which won't allow it to run. | |
| Aug 8, 2012 at 1:32 | comment | added | TecBrat | It's not the end of the world if it changes, but it's a pain when it does. The last HG admin set the perms of the "perms" script to 000, so hopefully that's enough. I'll chattr -a that dir and see what happens. | |
| Aug 8, 2012 at 1:30 | comment | added | TecBrat | Yeah, "should be". | |
| Aug 8, 2012 at 1:29 | comment | added | Gilles 'SO- stop being evil' | The real solution is not to run this script. Since you have a dedicated server, you should be able to control what runs on it. | |
| Aug 8, 2012 at 1:08 | history | asked | TecBrat | CC BY-SA 3.0 |