I want to use best practices here, so please explain why all the complicated steps are necessary. Wouldn't it just be easier to make the tomcat user and the tomcat group owner of everything and be done with it? sudo chown tomcat:tomcat -R /opt/tomcat My question is: why all the complicated setup? Why do we need to give the tomcat group ownership to some directories, the tomcat user owner to others, write access by the group to some files, read access to other files… … then make the tomcat user owner of certain directories … sudo chown -R tomcat /opt/tomcat/logs /opt/tomcat/temp /opt/tomcat/webapps/ /opt/tomcat/work/ /opt/tomcat/temp/ /opt/tomcat/logs/ … then give the tomcat group read access to all the configuration files … sudo chmod g+r -R /opt/tomcat/conf … then give the tomcat group write access to the configuration directory … sudo chmod g+rwx /opt/tomcat/conf The installation is simple and straight forward: sudo yum install java-1.8.0-openjdk-devel Create Tomcat system user Running Tomcat as a root user is a security risk and is not recommended. If not, install the latest version of JAVA or use the following yum command to install available Java from the default repositories. The instructions say to change the group ownership of /opt/tomcat to tomcat … sudo chgrp -R tomcat /opt/tomcat/conf Step 1: Installing and Configuring Java Before heading up for the Tomcat installation, make sure you must have JAVA installed on your Linux box to run Tomcat. I'm setting up Tomcat on Centos according to, but with a twist: I put Tomcat in /opt/apache-tomcat-8.5.6 and then set up a symbolic link: sudo ln -s /opt/apache-tomcat-8.5.6 /opt/tomcat
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |