<blockquote>
<p>My usage is [...]. Will your negate command have the same behaviour?</p>
</blockquote>
<p>Yes.</p>
<blockquote>
<p>isn't it negating the result? OK<->CRITICAL?</p>
</blockquote>
<p>That's what <code>negate</code> does by default, but not when using the command line options I suggested.</p>
<blockquote>
<p>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.</p>
</blockquote>
<p>Ah, good point.</p>
<p>With this reasoning, I guess the correctâ„¢ exit code would be <code>UNKNOWN</code>. Maybe these plugins should've returned that in the first place. However, it might now be better to make this configurable indeed.</p>
<p>So, I'm fine with merging your change. We should just add a test case.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br><a href='https://github.com/monitoring-plugins/monitoring-plugins/pull/1246#issuecomment-38261367'>Reply to this email on GitHub</a>.<img src='https://github.com/notifications/beacon/5514713__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxMTAxNDY4MywiZGF0YSI6eyJpZCI6Mjc2MTIzOTF9fQ==--ac58aeab90def0177f2b85eb363c9fb6f6db40a0.gif' height='1' width='1'></p>