reliable way to give all read/write access recursively in CentOS 7

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












What is the most reliable way to give all users read/write privileges for a given directory, all of its subdirectories, and files in CentOS 7?



In an eclipse web application project that uses Maven, I am getting the following compilation error in the pom.xml:



Parent of resource: /home/user/workspace/MinimalDbaseExample/target/m2e-wtp is marked as read-only. 


Since this sounds like a permissions issue, I typed in the following in the CentOS 7 terminal:



chmod -R ugo+rw /home/user/workspace/MinimalDbaseExample/target/


And I also tried:



chmod -R 0777 /home/user/workspace/MinimalDbaseExample


But eclipse is still showing the compilation error, even after multiple Project clean and Maven update operations. However, I am able to import the same zipped project file into a Windows version of eclipse, and there is no compilation error related to file permissions in the Windows version, so this causes me to wonder if perhaps my above chmod statements did not actually open up the file permissions in the CentOS 7 machine.



Is there a better statement syntax that can reliably open up read write permissions to all users for the given directory and all its recursive subdirectories and files?










share|improve this question























  • I'm not familiar with eclipse but maybe the read-only is something defined in the project rather than the file system? Another possibility is that some files are not owned by you so you cannot chmod them, but then chmod should have complained.
    – Bjorn Munch
    Apr 25 '15 at 6:51










  • @BjornMunch I am root.
    – CodeMed
    Apr 25 '15 at 6:52






  • 1




    You should also consider whether SELinux is causing this. You can temporarily disable it with sudo setenforce 0.
    – garethTheRed
    Apr 25 '15 at 7:07










  • Also, try namei -lx /home/user/workspace/MinimalDbaseExample/target/m2e-wtp which will shown you what's mounted where as well as permissions for the whole directory tree from root to leaf-node.
    – garethTheRed
    Apr 25 '15 at 7:20










  • @garethTheRed Thank you very much for looking into this. Please see EDIT to my OP describing the results. I am still experiencing the same problem. What else can I try?
    – CodeMed
    Apr 26 '15 at 20:51














up vote
1
down vote

favorite
1












What is the most reliable way to give all users read/write privileges for a given directory, all of its subdirectories, and files in CentOS 7?



In an eclipse web application project that uses Maven, I am getting the following compilation error in the pom.xml:



Parent of resource: /home/user/workspace/MinimalDbaseExample/target/m2e-wtp is marked as read-only. 


Since this sounds like a permissions issue, I typed in the following in the CentOS 7 terminal:



chmod -R ugo+rw /home/user/workspace/MinimalDbaseExample/target/


And I also tried:



chmod -R 0777 /home/user/workspace/MinimalDbaseExample


But eclipse is still showing the compilation error, even after multiple Project clean and Maven update operations. However, I am able to import the same zipped project file into a Windows version of eclipse, and there is no compilation error related to file permissions in the Windows version, so this causes me to wonder if perhaps my above chmod statements did not actually open up the file permissions in the CentOS 7 machine.



Is there a better statement syntax that can reliably open up read write permissions to all users for the given directory and all its recursive subdirectories and files?










share|improve this question























  • I'm not familiar with eclipse but maybe the read-only is something defined in the project rather than the file system? Another possibility is that some files are not owned by you so you cannot chmod them, but then chmod should have complained.
    – Bjorn Munch
    Apr 25 '15 at 6:51










  • @BjornMunch I am root.
    – CodeMed
    Apr 25 '15 at 6:52






  • 1




    You should also consider whether SELinux is causing this. You can temporarily disable it with sudo setenforce 0.
    – garethTheRed
    Apr 25 '15 at 7:07










  • Also, try namei -lx /home/user/workspace/MinimalDbaseExample/target/m2e-wtp which will shown you what's mounted where as well as permissions for the whole directory tree from root to leaf-node.
    – garethTheRed
    Apr 25 '15 at 7:20










  • @garethTheRed Thank you very much for looking into this. Please see EDIT to my OP describing the results. I am still experiencing the same problem. What else can I try?
    – CodeMed
    Apr 26 '15 at 20:51












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





What is the most reliable way to give all users read/write privileges for a given directory, all of its subdirectories, and files in CentOS 7?



In an eclipse web application project that uses Maven, I am getting the following compilation error in the pom.xml:



Parent of resource: /home/user/workspace/MinimalDbaseExample/target/m2e-wtp is marked as read-only. 


Since this sounds like a permissions issue, I typed in the following in the CentOS 7 terminal:



chmod -R ugo+rw /home/user/workspace/MinimalDbaseExample/target/


And I also tried:



chmod -R 0777 /home/user/workspace/MinimalDbaseExample


But eclipse is still showing the compilation error, even after multiple Project clean and Maven update operations. However, I am able to import the same zipped project file into a Windows version of eclipse, and there is no compilation error related to file permissions in the Windows version, so this causes me to wonder if perhaps my above chmod statements did not actually open up the file permissions in the CentOS 7 machine.



Is there a better statement syntax that can reliably open up read write permissions to all users for the given directory and all its recursive subdirectories and files?










share|improve this question















What is the most reliable way to give all users read/write privileges for a given directory, all of its subdirectories, and files in CentOS 7?



In an eclipse web application project that uses Maven, I am getting the following compilation error in the pom.xml:



Parent of resource: /home/user/workspace/MinimalDbaseExample/target/m2e-wtp is marked as read-only. 


Since this sounds like a permissions issue, I typed in the following in the CentOS 7 terminal:



chmod -R ugo+rw /home/user/workspace/MinimalDbaseExample/target/


And I also tried:



chmod -R 0777 /home/user/workspace/MinimalDbaseExample


But eclipse is still showing the compilation error, even after multiple Project clean and Maven update operations. However, I am able to import the same zipped project file into a Windows version of eclipse, and there is no compilation error related to file permissions in the Windows version, so this causes me to wonder if perhaps my above chmod statements did not actually open up the file permissions in the CentOS 7 machine.



Is there a better statement syntax that can reliably open up read write permissions to all users for the given directory and all its recursive subdirectories and files?







centos command-line permissions chmod






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 30 at 22:32









Jeff Schaller

37.4k1052121




37.4k1052121










asked Apr 25 '15 at 6:44









CodeMed

1,7582271100




1,7582271100











  • I'm not familiar with eclipse but maybe the read-only is something defined in the project rather than the file system? Another possibility is that some files are not owned by you so you cannot chmod them, but then chmod should have complained.
    – Bjorn Munch
    Apr 25 '15 at 6:51










  • @BjornMunch I am root.
    – CodeMed
    Apr 25 '15 at 6:52






  • 1




    You should also consider whether SELinux is causing this. You can temporarily disable it with sudo setenforce 0.
    – garethTheRed
    Apr 25 '15 at 7:07










  • Also, try namei -lx /home/user/workspace/MinimalDbaseExample/target/m2e-wtp which will shown you what's mounted where as well as permissions for the whole directory tree from root to leaf-node.
    – garethTheRed
    Apr 25 '15 at 7:20










  • @garethTheRed Thank you very much for looking into this. Please see EDIT to my OP describing the results. I am still experiencing the same problem. What else can I try?
    – CodeMed
    Apr 26 '15 at 20:51
















  • I'm not familiar with eclipse but maybe the read-only is something defined in the project rather than the file system? Another possibility is that some files are not owned by you so you cannot chmod them, but then chmod should have complained.
    – Bjorn Munch
    Apr 25 '15 at 6:51










  • @BjornMunch I am root.
    – CodeMed
    Apr 25 '15 at 6:52






  • 1




    You should also consider whether SELinux is causing this. You can temporarily disable it with sudo setenforce 0.
    – garethTheRed
    Apr 25 '15 at 7:07










  • Also, try namei -lx /home/user/workspace/MinimalDbaseExample/target/m2e-wtp which will shown you what's mounted where as well as permissions for the whole directory tree from root to leaf-node.
    – garethTheRed
    Apr 25 '15 at 7:20










  • @garethTheRed Thank you very much for looking into this. Please see EDIT to my OP describing the results. I am still experiencing the same problem. What else can I try?
    – CodeMed
    Apr 26 '15 at 20:51















I'm not familiar with eclipse but maybe the read-only is something defined in the project rather than the file system? Another possibility is that some files are not owned by you so you cannot chmod them, but then chmod should have complained.
– Bjorn Munch
Apr 25 '15 at 6:51




I'm not familiar with eclipse but maybe the read-only is something defined in the project rather than the file system? Another possibility is that some files are not owned by you so you cannot chmod them, but then chmod should have complained.
– Bjorn Munch
Apr 25 '15 at 6:51












@BjornMunch I am root.
– CodeMed
Apr 25 '15 at 6:52




@BjornMunch I am root.
– CodeMed
Apr 25 '15 at 6:52




1




1




You should also consider whether SELinux is causing this. You can temporarily disable it with sudo setenforce 0.
– garethTheRed
Apr 25 '15 at 7:07




You should also consider whether SELinux is causing this. You can temporarily disable it with sudo setenforce 0.
– garethTheRed
Apr 25 '15 at 7:07












Also, try namei -lx /home/user/workspace/MinimalDbaseExample/target/m2e-wtp which will shown you what's mounted where as well as permissions for the whole directory tree from root to leaf-node.
– garethTheRed
Apr 25 '15 at 7:20




Also, try namei -lx /home/user/workspace/MinimalDbaseExample/target/m2e-wtp which will shown you what's mounted where as well as permissions for the whole directory tree from root to leaf-node.
– garethTheRed
Apr 25 '15 at 7:20












@garethTheRed Thank you very much for looking into this. Please see EDIT to my OP describing the results. I am still experiencing the same problem. What else can I try?
– CodeMed
Apr 26 '15 at 20:51




@garethTheRed Thank you very much for looking into this. Please see EDIT to my OP describing the results. I am still experiencing the same problem. What else can I try?
– CodeMed
Apr 26 '15 at 20:51










1 Answer
1






active

oldest

votes

















up vote
6
down vote



accepted










You said you wanted to grant read and write permissions to all subdirectories and files under: /home/user/workspace/MinimalDbaseExample ... right?



Octal 0777 permissions grant rwxrwxrwx symbolically.



Octal 0755 permissions grant rwxr-xr-x symbolically.



Octal 0666 permissions grant rw-rw-rw- symbolically.



To set read/write/execute permissions to the /home/user/workspace/MinimalDbaseExample directory and all files and folders within it, choose which permission set you want, and do the following as an example:



1) Make your present working directory : /home/user/workspace



2) Type: chmod -R 0777 MinimalDbaseExample/



Following this procedure exactly, grants the folder MinimalDbaseExample/ and all files and subdirectories therein 0777/drwxrwxrwx permissions.



I tested this setting up some dummy directories under my '~' directory and verified it worked.



Credit goes to this thread, but it should not be at all this complex... I hope you make progress.



https://stackoverflow.com/questions/3740152/how-to-set-chmod-for-a-folder-and-all-of-its-subfolders-and-files-in-linux-ubunt






share|improve this answer






















  • I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
    – nomad.rc
    Apr 27 '15 at 6:52











  • The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
    – CodeMed
    Apr 27 '15 at 20:57










  • Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
    – CodeMed
    Jun 30 '15 at 23:21










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f198525%2freliable-way-to-give-all-read-write-access-recursively-in-centos-7%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
6
down vote



accepted










You said you wanted to grant read and write permissions to all subdirectories and files under: /home/user/workspace/MinimalDbaseExample ... right?



Octal 0777 permissions grant rwxrwxrwx symbolically.



Octal 0755 permissions grant rwxr-xr-x symbolically.



Octal 0666 permissions grant rw-rw-rw- symbolically.



To set read/write/execute permissions to the /home/user/workspace/MinimalDbaseExample directory and all files and folders within it, choose which permission set you want, and do the following as an example:



1) Make your present working directory : /home/user/workspace



2) Type: chmod -R 0777 MinimalDbaseExample/



Following this procedure exactly, grants the folder MinimalDbaseExample/ and all files and subdirectories therein 0777/drwxrwxrwx permissions.



I tested this setting up some dummy directories under my '~' directory and verified it worked.



Credit goes to this thread, but it should not be at all this complex... I hope you make progress.



https://stackoverflow.com/questions/3740152/how-to-set-chmod-for-a-folder-and-all-of-its-subfolders-and-files-in-linux-ubunt






share|improve this answer






















  • I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
    – nomad.rc
    Apr 27 '15 at 6:52











  • The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
    – CodeMed
    Apr 27 '15 at 20:57










  • Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
    – CodeMed
    Jun 30 '15 at 23:21














up vote
6
down vote



accepted










You said you wanted to grant read and write permissions to all subdirectories and files under: /home/user/workspace/MinimalDbaseExample ... right?



Octal 0777 permissions grant rwxrwxrwx symbolically.



Octal 0755 permissions grant rwxr-xr-x symbolically.



Octal 0666 permissions grant rw-rw-rw- symbolically.



To set read/write/execute permissions to the /home/user/workspace/MinimalDbaseExample directory and all files and folders within it, choose which permission set you want, and do the following as an example:



1) Make your present working directory : /home/user/workspace



2) Type: chmod -R 0777 MinimalDbaseExample/



Following this procedure exactly, grants the folder MinimalDbaseExample/ and all files and subdirectories therein 0777/drwxrwxrwx permissions.



I tested this setting up some dummy directories under my '~' directory and verified it worked.



Credit goes to this thread, but it should not be at all this complex... I hope you make progress.



https://stackoverflow.com/questions/3740152/how-to-set-chmod-for-a-folder-and-all-of-its-subfolders-and-files-in-linux-ubunt






share|improve this answer






















  • I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
    – nomad.rc
    Apr 27 '15 at 6:52











  • The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
    – CodeMed
    Apr 27 '15 at 20:57










  • Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
    – CodeMed
    Jun 30 '15 at 23:21












up vote
6
down vote



accepted







up vote
6
down vote



accepted






You said you wanted to grant read and write permissions to all subdirectories and files under: /home/user/workspace/MinimalDbaseExample ... right?



Octal 0777 permissions grant rwxrwxrwx symbolically.



Octal 0755 permissions grant rwxr-xr-x symbolically.



Octal 0666 permissions grant rw-rw-rw- symbolically.



To set read/write/execute permissions to the /home/user/workspace/MinimalDbaseExample directory and all files and folders within it, choose which permission set you want, and do the following as an example:



1) Make your present working directory : /home/user/workspace



2) Type: chmod -R 0777 MinimalDbaseExample/



Following this procedure exactly, grants the folder MinimalDbaseExample/ and all files and subdirectories therein 0777/drwxrwxrwx permissions.



I tested this setting up some dummy directories under my '~' directory and verified it worked.



Credit goes to this thread, but it should not be at all this complex... I hope you make progress.



https://stackoverflow.com/questions/3740152/how-to-set-chmod-for-a-folder-and-all-of-its-subfolders-and-files-in-linux-ubunt






share|improve this answer














You said you wanted to grant read and write permissions to all subdirectories and files under: /home/user/workspace/MinimalDbaseExample ... right?



Octal 0777 permissions grant rwxrwxrwx symbolically.



Octal 0755 permissions grant rwxr-xr-x symbolically.



Octal 0666 permissions grant rw-rw-rw- symbolically.



To set read/write/execute permissions to the /home/user/workspace/MinimalDbaseExample directory and all files and folders within it, choose which permission set you want, and do the following as an example:



1) Make your present working directory : /home/user/workspace



2) Type: chmod -R 0777 MinimalDbaseExample/



Following this procedure exactly, grants the folder MinimalDbaseExample/ and all files and subdirectories therein 0777/drwxrwxrwx permissions.



I tested this setting up some dummy directories under my '~' directory and verified it worked.



Credit goes to this thread, but it should not be at all this complex... I hope you make progress.



https://stackoverflow.com/questions/3740152/how-to-set-chmod-for-a-folder-and-all-of-its-subfolders-and-files-in-linux-ubunt







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 27 '15 at 7:19

























answered Apr 25 '15 at 7:07









nomad.rc

42629




42629











  • I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
    – nomad.rc
    Apr 27 '15 at 6:52











  • The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
    – CodeMed
    Apr 27 '15 at 20:57










  • Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
    – CodeMed
    Jun 30 '15 at 23:21
















  • I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
    – nomad.rc
    Apr 27 '15 at 6:52











  • The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
    – CodeMed
    Apr 27 '15 at 20:57










  • Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
    – CodeMed
    Jun 30 '15 at 23:21















I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
– nomad.rc
Apr 27 '15 at 6:52





I revised my post you could try this instead, as @garethTheRed suggests, it should be quite straightforward unless SELinux or some other layer is in some way making this more complex then usual.
– nomad.rc
Apr 27 '15 at 6:52













The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
– CodeMed
Apr 27 '15 at 20:57




The solution was to move the project to a different eclipse workspace on the same CentOS devbox, and let eclipse manage the permissions.
– CodeMed
Apr 27 '15 at 20:57












Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
– CodeMed
Jun 30 '15 at 23:21




Thank y0u and +1. This problem emerged on a different machine. In the new situation, your revised two step solution above worked.
– CodeMed
Jun 30 '15 at 23:21

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f198525%2freliable-way-to-give-all-read-write-access-recursively-in-centos-7%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay