Get rid of ANNOYING bug due to lack of SO_REUSEADDR #1
Conversation
This file contains hidden or 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
As we all know from olden days when you run a server app with a listen socket, you need to set SO_REUSEADDR or else you won't be able to bind it again if you restart it and old client sockets are still lingering.
Owner
|
You are right. Please do not include the hidden config files: the paths differ for every user. I will merge if these files are excluded (and best added in gitignore). Also this is a very old version of quisk and we may think about updating to the newest version (but this version is working for me since years). |
Author
|
I'm sorry, I thought I was using the latest version. I don't have the computer with my checked out source anymore but it's a very small change, would you consider adding it manually? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As we all know from olden days when you run a server app with a listen socket, you need to set SO_REUSEADDR or else you won't be able to bind it again if you restart it and old client sockets are still lingering. This causes WSJT to fail to start and you have to wait.