Detailed tutorial on running configuration examples

In the cloud server ECS Linux system, usually when we execute some tasks that take a long time to run, we must wait until the execution is completed before disconnecting the SSH connection or closing the client software, otherwise the execution may be interrupted. This article introduces several methods to ensure that the program continues to run after the user logs out. Use the management terminal to log in to the local session (console) port of the server through the management terminal. Programs executed in this terminal will not be affected by the exit of the SSH login user. The specific operation methods are as follows: 1. Log in to the server through the management terminal. 2. Execute the required program or script. 3. The next time you need to check the task execution status, just connect to the management terminal again to check. Use nohup to execute nohup. As the name suggests, it prevents subsequent commands from responding to the SIGHUP signal. In other words, after executing nohup through remote login, the program will still execute normally even after logging out. Normally, the nohup command will be followed by an & character at the end, indicating that this

1. Detailed introduction to the configuration method of keeping the process running after the SSH client in Linux is disconnected

Introduction: In the cloud server ECS Linux system, usually when we perform some tasks that take a long time to run, You must wait until the execution is completed before disconnecting the SSH connection or closing the client software, otherwise the execution may be interrupted

2. When eclipse runs php, the running configuration, and the debugging configuration Settings

Introduction: When eclipse runs PHP, run configuration, and debugging configuration settings

3. eclipse run When eclipse runs PHP, the running configuration, and the debugging configuration settings have been mentioned in a previous blog, so there will be no more details here. Having said that, for the installation of eclipse, you can refer to the following blog: eclipse installation http://jingyan.baidu.com/album/d7130635194f1513fcf47557.htmlphp plug-in installation http://www.jb51.ne

4.

Import solr running configuration and database data into solr

Introduction: 1. Run 1, solr running container, tomcat 2, copy apache-solr- 3.6.0.war to tomcat's webapps directory and renamed solr.war 3. Create two folders with the structure conf/Catalina/localhost in tomcat's conf directory. Create two folders with the structure solr-tomcat/solr (solr's HOME directory), such as building them in the root of D disk

5.

Test configuration for JBuilder2005 unit testing experience _MySQL

#Introduction: In the last step of the test case wizard, you are allowed to create a running configuration item for the test case, as shown in the figure below: Picture error! There is no text with the specified style in the document. Create a running test item In general, you do not have to create a separate running configuration item for each test case class. JBuilder will use the default running configuration to run the test case. Test run configuration items are required

The above is the detailed content of Detailed tutorial on running configuration examples. For more information, please follow other related articles on the PHP Chinese website!