Addition of migrid init script PID file saving when not handled natively #173
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… nor the daemons themselves do that. Namely, support the containerized cases where init is tini or similar instead of systemd.
|
Merged through svn - the flagged py2 lint failure was a ubuntu repo timeout. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adjust init script to explicitly write PID files when neither
systemdnor the daemons themselves do that. Namely, support the containerized cases where init istinior similar instead ofsystemdand the existingstopactions fail because they can't find a saved service PID to kill.Needed in order to enable wider use of the migrid init script for service checks and management e.g. in
checkmigsslcron job for containerized deployments and for thedocker-entry.shstart up script of docker-migrid.