ntpd not adjusting the clock?

[Peter A. Giessel]

On 2006/10/17 14:40, Derek Ragona seems to have typed:
> ntpd won't correct the clock if the difference is too large.  So you need 
> to kill ntpd, run ntpdate to set the clock, then start ntpd up again.
> 
>          -Derek
> 
> 
> At 05:13 PM 10/17/2006, Zbigniew Szalbot wrote:
>> ntpd_flags="-g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntp.drift"

>From "man ntpd":
     -g      Normally, ntpd exits if the offset exceeds the sanity limit,
             which is 1000 s by default.  If the sanity limit is set to zero,
             no sanity checking is performed and any offset is acceptable.
             This option overrides the limit and allows the time to be set to
             any value without restriction; however, this can happen only
             once.  After that, ntpd will exit if the limit is exceeded.  This
             option can be used with the -q option.

With the "-g" flag in there, it shouldn't matter if the difference is
too large.