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

Using SO_REUSEPORT is extremely counterintuitive #1553

Closed
tomjaguarpaw opened this Issue Jul 27, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@tomjaguarpaw
Contributor

tomjaguarpaw commented Jul 27, 2017

Using SO_REUSEPORT for binding sockets is extremely counterintuitive. It's far more likely that I will reuse the wrong port by accident than it is that I really wanted to share the port. Is there any chance this behaviour could be placed behind an option?

@tilgovi

This comment has been minimized.

Collaborator

tilgovi commented Aug 6, 2017

Sounds sensible. I would welcome a PR for that.

@tilgovi

This comment has been minimized.

Collaborator

tilgovi commented Aug 6, 2017

I am not sure what the right default is, though.

@benoitc

This comment has been minimized.

Owner

benoitc commented Aug 18, 2017

not sure i understand, what is the ticket for?

@tilgovi

This comment has been minimized.

Collaborator

tilgovi commented Aug 18, 2017

The ticket is to make SO_REUSEPORT opt-in.

@benoitc

This comment has been minimized.

Owner

benoitc commented Sep 18, 2017

closing in favour of #1603

@benoitc benoitc closed this Sep 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment