signal: reset signal counters after fork (#3483) #3485
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
If a signal was received but was not dispatched before fork then caught_signals counter should be reset. Closing of signal pipe makes imposible to receive the signal that was counted. There is no need in this signal because it was sent to parent process
bnoordhuis
reviewed
Feb 17, 2022
|
Is there anything I can do with this PR? Any improvements? |
|
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
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.
If a signal was received but was not dispatched before fork then
caught_signals counter should be reset. Closing of signal pipe makes
imposible to receive the signal that was counted.
There is no need in this signal because it was sent to parent process
See full description in issue #3483
#3483