Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W wdscripts
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Diese GitLab Instanz ist nicht für den produktiven Einsatz gedacht!
Bitte https://gitlab.ost.ch benutzen!
Diese Instanz ist nur nuch zur Datenmigration online.

Vielen Dank für euer Verständnis.

  • ifs
  • coast
  • wdscripts
  • Issues
  • #3

Closed
Open
Created Dec 20, 2016 by Marcel Huber@m1huberOwner

More verbose and lenient RUN_SERVICE check

In prjconfig.sh the following two variables can be defined:

  • RUN_SERVICE_CFGFILE
  • RUN_SERVICE

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 server => will not execute, because it was disabled (RUN_SERVICE=0)!

  1. Print the path to the RUN_SERVICE_CFGFILE too, this would help operators identify and/or fix the issue.
  2. This setting should not block status or stop calls, instead issue a warning if application starting is disabled by configuration.
Assignee
Assign to
Time tracking