Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
At my office, we have a network directory structure like this:
/jobs/2004/3999-job_name/... /jobs/2004/4000-job_name/... The issue is that employees rename the ‘4000-job_name’ folders (which in turn breaks other things that rely on the name being consistent with a database).
How can I stop users from renaming the parent folder while still allowing them full control of that folder’s contents?
Please keep in mind that this is a Samba share that Windows users will be accessing.
I think you want to do this:
Since the directories
/jobs/*are in fact files in/jobstheir names cannot be changed without the write permission for/jobs. In the subdirectories of/jobs/everyone is allowed to do anything with the commands above.Also, be sure to set the permissions of new directories to rwx as you add them.
(edit by Bill K to fix the examples–the solution was correct but he misread the question due to the strange coloring SO added)