-
Notifications
You must be signed in to change notification settings - Fork 10
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
Configurable exit code #238
Comments
Hello @PenelopeFudd 🙂 I can image supporting these conditions:
and I will allow users to specify any combination of these conditions (like do you think this makes sense @PenelopeFudd?
Thanks, glad to hear that 🙂 |
Yes, that's exactly it, thank you! |
Hello @PenelopeFudd, I have released a new version |
Er, one more request: |
hmm, I understand, that it can be a little bit tedious to list all the conditions. I am struggling with the semantics of such option |
It's true that it could be interpreted in many ways, although I was thinking of the basic "any of the errors that could be specified with --fail", as a way to see if everything is perfect or not. If I start looking into negative or truncated answers, then it'd be time to explicitly list what counts as an error. |
Describe the feature
I'd like to have dnspyre return a nonzero exit code if any requests failed. Different people might have different definitions of failure at different times (e.g. connect timeout, nxdomain, duplicate answers, wrong answers, bad certificate, etc), so the parameter might take an argument:
--fail="timeout,nxdomain"
Why do you need this feature
I have a program that does binary searches. It'll run a specified program and fill in a specified parameter with a number, and based on the return code of the program, will search until it finds the number where the program just starts to fail:
Without this feature, I have to write a wrapper script that runs dnspyre and then greps for a success or failure string.
For an example, see the
--fail
argument forcurl
.Thanks!
PS: This looks like the best DNS benchmarking program out there! DNSperf / DNSRes are hard to use, Flamethrower is hard in a different way, and DNS shotgun is... weird? Dnspyre looks polished, and it has all the protocols I'm looking for.
The text was updated successfully, but these errors were encountered: