-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Should we have SO_REUSEADDR on listening sockets? #1267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Still valid. |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Keep |
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future. |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions. |
Closing a listening socket that has open connections leaves the socket in a TIME_WAIT state for approximately 2 minutes. This prevents the socket from being reused immediately. IMHO on an embedded device this is not very useful because we will most likely start the same server on the same port anyway.
Setting the SO_REUSEADDR on the listening socket would make the port available immediately again.
The text was updated successfully, but these errors were encountered: