Actually, I was inclined to hardcode <code>+tries=1</code> on the <code>dig(1)</code> command line. While the <code>dig(1)</code> command happens to implement retries by default, most of our plugins don't, because users might want to notice if some fraction of queries fail, and because Nagios & friends support "soft states" if users don't want to be notified in such cases. I'd be surprised if the original <code>check_dig</code> author consciously relied on these <code>dig(1)</code> semantics. And yes, maybe the disagreement is "philosophical": I do not at all believe that more configuration switches are necessarily better. Only those that might actually be useful are good :-) But I'll agree that there are many cases where you could argue one way or the other. Either way, if there's just one more comment on this single line of code, I'll revert to the floating point division, which I agree is totally fine as well ;-) — Reply to this email directly or <a href='https://github.com/monitoring-plugins/monitoring-plugins/commit/e33ecc84c7ebdf4af3e8649a326e8a5acc9fe5b6#commitcomment-5230669'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/5514713__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwNjY0Nzk0NSwiZGF0YSI6eyJpZCI6MjQ2MDgyMTB9fQ==--d78472945a078b16ea4c56899ddcc15eb482ae50.gif' height='1' width='1'>