-
Notifications
You must be signed in to change notification settings - Fork 435
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
The effect of the timeout option might surprise users #3
Comments
I concur -- using alpine:3.6 docker image:
So, 2m7s multiple by 15 iterations and you are looking at ~30min "hang" with zero output being logged. |
What do you get with |
@ianfixes Easy to test:
|
Aah, that's a nice one-liner! I put the
|
FYI, feel free to use my solution:
|
The problem is that the
There's also the |
The timeout is implemented by doing N attempts and waiting one second between each attempt. If the attempt isn't instantaneous, the effective timeout balloons. Some versions of netcat allow you to control the tcp connection timeout. The version of netcat that shipped with my copy of macos sierra takes 75 seconds to timeout by default:
The text was updated successfully, but these errors were encountered: