index 8b5fe4d032ce738645d926aad06005c7c61ada3b..20780b5507451020eb9b5b2043d856ea0bb8b1ca 100755 (executable)
# An offset of 0.000000 with an error is probably bogus. Actually,
# it's probably always bogus, but let's be paranoid here.
# Has been reported that 0.0000 happens in a production environment
- # so this check should be taken out - SF tracker 1150777
+ # on Solaris 8 so this check should be taken out - SF tracker 1150777
#if ($offset == 0) { undef $offset;}
$ntpdate_error = defined ($offset) ? $ERRORS{"OK"} : $ERRORS{"CRITICAL"};
@@ -443,7 +443,7 @@ Checks the jitter/dispersion of clock signal between <host> and its sys.peer wit
-j (--jwarn)
Clock jitter in milliseconds at which a warning message will be generated.\n Defaults to $DEFAULT_JITTER_WARN.
-k (--jcrit)
- Clock jitter in milliseconds at which a warning message will be generated.\n Defaults to $DEFAULT_JITTER_CRIT.
+ Clock jitter in milliseconds at which a critical message will be generated.\n Defaults to $DEFAULT_JITTER_CRIT.
If jitter/dispersion is specified with -j or -k and ntpq times out, then a
warning is returned.\n