Setting SO_KEEPALIVE only for network connections #785
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In the socket setup SO_KEEPALIVE (enabling TCP keepalive) is set after the if-branch between local unix and network sockets, setting it for both socket types. This works on Linux, but on Windows Subsystem for Linux, the
sock.setsockopt()call returns EINVAL, which - while different from Linux - can be argued to make sense since a local unix socket can't really have a TCP keepalive setting.By moving the SO_KEEPALIVE
sock.setsockopt()call into the branch for network connections, it works on Wndows as well.