Skip to content

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

Closed
everslick opened this issue Mar 27, 2018 · 7 comments
Closed

Should we have SO_REUSEADDR on listening sockets? #1267

everslick opened this issue Mar 27, 2018 · 7 comments
Labels
Status: Stale Issue is stale stage (outdated/stuck)

Comments

@everslick
Copy link
Contributor

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.

@stale
Copy link

stale bot commented Aug 1, 2019

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 stale bot added the Status: Stale Issue is stale stage (outdated/stuck) label Aug 1, 2019
@everslick
Copy link
Contributor Author

Still valid.

@stale stale bot removed the Status: Stale Issue is stale stage (outdated/stuck) label Aug 1, 2019
@stale
Copy link

stale bot commented Sep 30, 2019

[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 stale bot added the Status: Stale Issue is stale stage (outdated/stuck) label Sep 30, 2019
@everslick
Copy link
Contributor Author

Keep

@stale
Copy link

stale bot commented Oct 1, 2019

[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future.

@stale stale bot removed the Status: Stale Issue is stale stage (outdated/stuck) label Oct 1, 2019
@stale
Copy link

stale bot commented Nov 30, 2019

[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 stale bot added the Status: Stale Issue is stale stage (outdated/stuck) label Nov 30, 2019
@stale
Copy link

stale bot commented Dec 14, 2019

[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale Issue is stale stage (outdated/stuck)
Projects
None yet
Development

No branches or pull requests

1 participant