[DAEMON-342] Procrun does not support accuratly the service lifecycle states

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 1.0.15
• Component/s: Procrun
• Assignee: Unassigned
• Reporter: Johannes Meier
• Created: 09/Dec/15 15:55
• Updated: 09/Nov/16 17:06
• Resolved: 09/Nov/16 17:06

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.

Issue Links

• duplicates: DAEMON-258 prunsrv to block until start method returns