In RedHat and Centos changing the startup scripts as stated here worked perfectly fine.

But Suse seems to follow different rules, if so what are the changes need to be taken into consideration?

Do "CHKCONFIG" in init scripts will have any effect of the starting order of services?


In Suse start and stop order of services are managed by insserv package and based on dependency with other services. So it is little different. The answer to your question is given in details with examples in the following Suse article:

Manipulating the start and stop order of Linux services

Under the LSB (Linux Standards Base), the start and stop order of services is controlled using the "insserv" package. Unlike Netware, DOS and other operating systems, SUSE calculates the start and stop orders based on dependencies. This idiosyncrasy of Linux has the distinct advantage of providing a faster boot time, but does make things a little more complex.


Here are few examples of how to manipulate the header of a service defined in /etc/init.d.

The following example will start Service "myService" after the network has loaded and will automatically start the service "myOtherService"

# Provides:        myService
# Required-Start: $network
# Should-Start:   myOtherService
# Required-Stop:
# Should-Stop:
# Default-Start:  2 3 5
# Default-Stop:
# Description:    Example Service
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.