From: B.Yanchitsky on
On Feb 1, 9:01 pm, kaukasoina708n8s6l...(a)sci.fi (Petri Kaukasoina)
wrote:
> It takes a few minutes before the ntpd server at 192.168.0.30 thinks it is
> syncronized to the local clock. iburst should make it faster. So change it
> at the server to this:
>
> server 127.127.1.0 iburst
> fudge 127.127.1.0 stratum 11

No effect, there must be minutes passed to obtain the time from the
server.
Very freaky ntpd is.

---
Bogdan
From: microsys on
B.Yanchitsky(a)gmail.com wrote:
> On Feb 1, 9:01 pm, kaukasoina708n8s6l...(a)sci.fi (Petri Kaukasoina)
> wrote:
>> It takes a few minutes before the ntpd server at 192.168.0.30 thinks it is
>> syncronized to the local clock. iburst should make it faster. So change it
>> at the server to this:
>>
>> server 127.127.1.0 iburst
>> fudge 127.127.1.0 stratum 11
>
> No effect, there must be minutes passed to obtain the time from the
> server.
> Very freaky ntpd is.
>
> ---
> Bogdan

This site may prove helpful. http://www.ntp.org/

The problem appears to be the clock on the computer you are attempting
to sync to (the reference computer) is too far out of sync and ntpd on
the reference computer is rejecting the call to act as a reference. The
reference computer is simply saying, go away your not even in the same
ball park.

The simple solution is to run, as a cron job, from the command netdate
ip of computer you want to sync to. Of course you do this on the
computer you want to sync up to the time reference. The cron job can be
run every 20 minutes or a longer interval ( say, every hour ) depending
on drift.

Using ntp is much nicer but does require a simple configuration file on
both the reference computer and computers wanting to use it as a
reference. When using ntp it's always a good idea to run {ntpdate ip} of
reference computer on boot up on any computer wanting to get a time
reference. This can be started rc.local.