My usage is /path/to/check_time -H ntp.xs4all.nl --warning-variance=2 --critical-variance=60 --timeout-warning
> 60 seconds time diff: CRITICAL > 2 seconds time diff: WARNING server ntp.xs4all.nl unavailable: WARNING (not critical) Will your negate command have the same behaviour? isn't it negating the result? OK<->CRITICAL? Even if it works, I'm not sure if I like your solution. It's not very obvious what is does, my solution seems more self-documenting. As for the generic solution: The time server being used, is NOT the time server being watched. There are not many tests where a host is used that is not the primary target for the test. check_http tests a http server and it's response. A timeout on this test is an issue that can be dealt with. I doubt a --timeout-warning commandline switch would be useful on other tests. In fact: I had the code for it in other checks, thought about it, and removed it for this pull request. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1246#issuecomment-38179972
