Suse service startup sequence analysis

I was finally excited about the Suse service startup sequence. I had to take a serious look at it. In the past, when I used Redhat, I used chkconfig to adjust the sequence of startup scripts. For example, # chkconfig: 35 98 01 indicates that I want to enable this service when runlever 3 and 5, and disable it in other cases. The start sequence is 98, which is very backward. The stop sequence is 01, which is quite advanced. However, in SLES, everything has changed. This method is no longer useful (Note: It is not useless, it is limited ). SUSE introduces a new method for configuring the startup sequence, which is called before/after. The related command used is insserv. The configuration method is to add some comments to the script, which is correct, just like this: www.2cto.com ### begin init info # Provides: Tomcat # Required-Start: $ network oracle-xe # Required-Stop: $ network # Default-Start: 2 3 5 # Default-Stop: 0 1 2 6 # Description: start Tomcat server ### end init info here, Provides: Specifies the name of the program or service controlled by the init script. Required-Start: Specifies the name of the service to be started before the service starts. Required-Stop: indicates the name of the service that needs to be stopped before the service is stopped. Default-Start: Specifies the runlevel level for automatic service startup. Default-Stop: indicates the runlevel of automatic service Stop. Description: service Description.
Then, run the command insserv. The insserv command will check the content of this part of the script, corresponding to the Default-Start and Default-Stop definitions, in the corresponding runlevel (/etc/init. d/rc ?. D/) create a script in the/etc/init. d/directory to start and stop the link. Insserv also writes the startup and stop dependencies between services to the file. depend. start file and. depend. stop. Oh, my God, it seems that the SUSE processing method is still full, so you don't have to worry about setting the startup sequence number for the script. In addition, the dependency can be automatically written to automatically create the corresponding STARTUP script (in fact, only the startup sequence number is given and a link to the startup script is created ). Www.2cto.com it is said that SUSE handles the startup script in compliance with a standard called LSB. If you are interested, click here. So what are the restrictions on using chkconfig to configure the startup script in SUSE? It can only be solved simply in/etc/init. d. Of course, no dependency is created. So can we use this handsome configuration method in SUSE in Redhat? If we have installed the LSB package, it seems that we can. Author: jackyyen