[ntp:questions] ntpdate works, but ntpd doesn't (reach = 0)
martin.burnicki at meinberg.de
Thu Feb 12 09:04:19 UTC 2009
> Harlan Stenn <stenn at ntp.org> writes:
>>>>> In article <mf5866-o44.ln1 at gateway.py.meinberg.de>, Martin Burnicki
>>>>> <martin.burnicki at meinberg.de> writes:
>>Martin> The basic thing I don't understand in the context of this thread
>>is Martin> why the behaviour with -g should not become the default
>>behaviour Martin> for ntpd.
>>Because -g overrides a sanity check.
>>It is better to actively override a sanity check than it is to require an
>>active action to provide a sanity check.
> The sanity check is whether or not the clock it too far off. When ntp is
> started it is expected that the clock is way off, and that the sanity
> check becomes an insanity check. Ie, if the system behaves badly in
> situations where everything is behaving as expected, then that is not a
> useful sanity check.
This exacly meets my point.
More information about the questions