Add signal handling to orch and node event loops. #71
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
Merged
engelmi
reviewed
Jan 23, 2023
engelmi
reviewed
Jan 24, 2023
engelmi
approved these changes
Jan 24, 2023
Signed-off-by: Steve Dunnagan <sdunnaga@redhat.com>
sdunnagan
force-pushed
the
signal_handler_2
branch
from
36028a4
to
12c02c1
Compare
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.
Signed-off-by: Steve Dunnagan sdunnaga@redhat.com
This PR addresses issue #67. Now if a SIGTERM signal is sent to hirte or hirte-node processes, registered handlers are invoked by their respective event loops. These handlers can initiate whatever clean-up is needed, and then exit the event loops.