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

Should fail if <port> isn't available on IPv4 #219

Closed
metrictwo opened this issue Oct 14, 2016 · 2 comments
Closed

Should fail if <port> isn't available on IPv4 #219

metrictwo opened this issue Oct 14, 2016 · 2 comments

Comments

@metrictwo
Copy link

Right now, carbon-c-relay seems to successfully start as long as its configured port is available on any combination of IPv4/IPv6 and TCP/UDP on any IP. For example, it will start even its TCP port is taken on all IPv4 addresses. This makes service management quite a bit harder, since we have to use other means to determine if it's actually listening on port TCP port 2003 on IPv4, which is quite unusual.

@grobian
Copy link
Owner

grobian commented Oct 15, 2016

I agree, and would like to go one step further than pull #220 and always require successful binding to all supported protos. Otherwise the setup is inconsistent and unpredictible, quoting you "quite unusual".

@justincmoy: that said, care to remove the -A from your patch and unconditionally require all ports to be bound? Thanks!

grobian added a commit that referenced this issue Oct 15, 2016
@grobian
Copy link
Owner

grobian commented Oct 15, 2016

merged and fixed

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

No branches or pull requests

2 participants