Uploaded image for project: 'Commons Daemon'
  1. Commons Daemon
  2. DAEMON-342

Procrun does not support accuratly the service lifecycle states

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Duplicate
    • 1.0.15
    • None
    • Procrun
    • None

    Description

      It is not possible to show accurately the different states of a service.
      A service has the states: starting, started, stopping , stopped
      An example for the starting/started phase:
      I can tell procrun which start method to use, maybe start().
      Procrun starts my start() method and as written in the documentation the start method does not return until service has stopped.
      Procrun does not know if my service has finished the starting period
      it tells windows my service has started but it is still starting.
      A second service which depends on the started service beliefs the service is already working now.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jomei Johannes Meier
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: