fix PPPOE SIGTERM #35
Merged
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
The daemon does not quit in case of a SIGTERM when a PPPoE session is established but there is no PPPOE signaling traffic. We can notice that it keeps blocking on recvmmsg() syscall: [pid 262269] recvmmsg(46, <unfinished ...> [pid 262268] recvmmsg(44, <unfinished ...> [pid 262264] recvmmsg(43, <unfinished ...> Those fd are: gtp-guard 262250 root 43u pack 4610713 0t0 PPP_SES type=SOCK_RAW gtp-guard 262250 root 44u pack 4641817 0t0 PPP_DIS type=SOCK_RAW gtp-guard 262250 root 46u pack 4629533 0t0 PPP_SES type=SOCK_RAW
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.
The daemon does not quit in case of a SIGTERM when a PPPoE session is established but there is no PPPOE signaling traffic.
We can notice that it keeps blocking on recvmmsg() syscall:
Those fd are: