This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
Process exit code not set when service fails to start/stop gracefully (v7) #120
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The host uses (old) version 0.8.0 of the Topshelf project which seems to incorrect set the exit code when an errors happens during start/stop. An error could be as described in #119.
This PR is basically a workaround for the Topshelf error by calling
Environment.Exit(int)
ourselves. This results in the windows service to actually fail which results in Windows Service Recovery to kick in.