Skip to content
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

Emit warning (instead of fatal error) when failing to set TCP Fast Open #368

Merged
merged 1 commit into from Jun 19, 2015

Conversation

kazuho
Copy link
Member

@kazuho kazuho commented Jun 19, 2015

In #356 we have added support for TCP Fast Open which is enabled by default (if TCP_FASTOPEN is defined in the header files).

However, people may use the server complied in an environment with TCP_FASTOPEN defined, and use the binary in an environment (i.e. kernel) that does not support the feature (see the comments on the pull-req). In such situation, the server fails to boot up due to the fact that it exits with a fatal error if setsockopt(TCP_FASTOPEN) fails.

This PR changes how the error is being handled. Instead of refusing to start, the server now just emits a warning and continues to operate if setsockopt(TCP_FASTOPEN) fails.

@kazuho kazuho changed the title Emit warning (instead of fatal error) when failing to set TCP Fast OPen Emit warning (instead of fatal error) when failing to set TCP Fast Open Jun 19, 2015
kazuho added a commit that referenced this pull request Jun 19, 2015
…cp-fastopen

Emit warning (instead of fatal error) when failing to set TCP Fast Open
@kazuho kazuho merged commit f882632 into master Jun 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant