More verbose and lenient RUN_SERVICE check
|Target version:||COAST - CoastRelease 201512|
In prjconfig.sh the following two variables can be defined:
These can be used to suppress an application from starting (using bootScript.sh or startwda.sh). Apparently also from stopping or querying the status.
In case the service is disabled, the following error is given:
Stopping <Application> server => will not execute, because it was disabled (RUN_SERVICE=0)!
- Why not print the path to the RUN_SERVICE_CFGFILE too, this would help operators identify and/or fix the issue
- Why should this setting also block status (and even stop) calls? Maybe on these operations there could just be a warning, as the feature is supposed to stop applications from starting