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?
Best Answer
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