Should i run tomcat as root

Run Ant target : select this option to run an Ant target. In the dialog that opens, select the target to be run. Run Grunt task : select this option to run a Grunt task. In the Grunt task dialog that opens, specify the Gruntfile. Specify the location of the Node. Run gulp task : select this option to run a Gulp task. In the Gulp task dialog that opens, specify the Gulpfile.

Run Maven Goal : select this option to run a Maven goal. In the dialog that opens, select the goal to be run. Run npm script : select this option to execute an npm script. Compile TypeScript : select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.

If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched. In the dialog that opens, specify where your CoffeeScript source files are located. Run Rake task : add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button , and select the desired task from the list of available tasks. Note that code completion is available here.

Run JRuby compiler : choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters if any. Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list. Otherwise, if the checkbox is cleared, the tool window is hidden.

Server tab for a local configuration Item Description Application server Select the server configuration to be used. After launch Select this checkbox to start a web browser after starting the server and deploying the artifacts. With JavaScript debugger If this checkbox is selected, the web browser is started with the JavaScript debugger enabled.

VM options If necessary, specify the command-line options to be passed to the server JVM at the server start. When specifying JVM options, follow these rules: Use spaces to separate individual options, for example, -client -ea -Xmxm.

Item Description Application server Select the server configuration to be used. After launch Select this checkbox to start a web browser after connecting to the server and deploying the artifacts.

The options are: Hot swap classes. Show dialog Select this checkbox if you want to see the Update dialog every time you use the Update application function. Remote staging This section contains the settings related to staging. Type Select the way the staging environment or host is accessed for transferring the application artifact or artifacts from your local computer.

The available options are: Same file system. Host If Same file system is selected for Type , the only available option for Host is also Same file system. Select an existing configuration or create a new one. The rest of the settings don't matter. Staging When deploying to the remote host, the application artifact or artifacts are placed into a staging folder which should be accessible to Tomcat. Path from root The path to the staging folder relative to the local or mounted folder, or the root of the S FTP host.

Mapped as The absolute path to the staging folder in the local file system of the remote host. Remote connection settings The settings for accessing deployed applications. Host The fully qualified domain name or the IP address of the Tomcat host.

Application context Specify the context root for an artifact or external resource: select the artifact or the resource and type or select the context root. Item Description Is Active Select checkboxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window. Log File Entry The read-only fields in this column list the log files to show.

The list can contain: Full paths to specific files. Skip Content Select this checkbox to have the previous content of the selected log skipped. Save console output to file Select this checkbox to save the console output to the specified location. Show console when a message is printed to standard output stream Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.

Show console when a message is printed to standard error stream Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard. Click this button to remove the selected log entry from the list. Item Description Choose code coverage runner Select the desired code coverage runner.

Sampling Select this option to measure code coverage with minimal slow-down. Tracing Select this option to collect accurate branch coverage. Track per test coverage Select this checkbox to detect lines covered by one test and all tests covering line. Packages and classes to record code coverage data If necessary, specify the classes and packages to be measured. Enable coverage in test folders. Select this checkbox to include the test source folders in code coverage analysis.

Startup script Specify the script to be used to start the server. Use default: If this checkbox is selected, the default script is used. Clear this checkbox to change the parameters passed to the script or to specify a different script: To specify the script, click and select the desired script in the dialog that opens.

When specifying the parameters and options, follow these rules: Use spaces to separate individual parameters and options, for example, -client -ea -Xmxm. Shutdown script Specify the script to be used to stop the server. Pass environment variables To pass specific variables to the server environment, select this checkbox and specify the variables: To add a variable, click and specify the variable name and value in the Name and Value fields respectively. Port Use this field to change the debugger port.

Debugger Settings Click this button to edit the debugger options on the Debugger page of the Settings dialog. Allow parallel run Select to allow running multiple instances of this run configuration in parallel. Store as project file Save the file with the run configuration settings to share it with other team members. Note that you cannot delete default configurations.

Click this button to sort configurations in the alphabetical order. Enter Click this icon to edit the selected task. Make the necessary changes in the dialog that opens. Active Oldest Votes. You should make a distinction between two concepts: The credentials of the Tomcat process. This should run as an unprivileged user: user tomcat , group tomcat in your example.

This way Tomcat can not perform any operation reserved to user root cf. The file permissions on Tomcat's files cf. Unix modes. Most of these files can easily be read-only for the Tomcat process and probably should. This is usually obtained by setting the owner of these files to root only the owner can change file permissions , the group to tomcat and removing the w permission flag for the group and others.

Improve this answer. Piotr P. Karwasz Piotr P. Karwasz 4, 2 2 gold badges 7 7 silver badges 19 19 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Mike Millson. Post by waimun Hi, Has anybody tried running tomcat as a non-root user in Linux? If so, how do you proceed ie. Pls advice. Thanks alot!

Turner, John. Ben Ricker. Post by Turner, John assume a user named 'tomcat' already created, and a group named 'tomcat' already created. You shouldn't have to change the permissions on any of the Tomcat files from what they are in a default install I never have.

Hi, Has anybody tried running tomcat as a non-root user in Linux?