Only allow one k0sctl to run simultaneously per host #382
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
jnummelin
reviewed
May 5, 2022
twz123
reviewed
May 5, 2022
Cant use configurer before detect OS Flock Wait a while No flock? Take a risk Seal window
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.
Fixes #381
Uses a lock file (
/run/lock/k0sctl) to stop multiple instances of k0sctl from operating on the same target host simultaneously. A background loop touches the modtime of the lock file every 10 seconds while k0sctl is running.If a lock file is found, it is discarded if it is over 30 seconds old.