Also, if the client and server are too far off, they will never
synchronize.
NTP is designed to synchronize a pool of servers by consensus. It
sees localhost as one of those servers. If any of the servers get too
far off from the average, that server's results are thrown out until
it comes back in range.
So if you've only got two machines, localhost and your designated
timeserver, they've got to be already pretty close before the NTP
daemon will maintain sync.
So what you want to do is to set your local time to *exactly* the
server time on startup, then let the ntp daemon maintain sync from
there on out.
There's a program called "ntpdate" that can do that initial
synchronization before the ntp daemon takes over.
On Wed, Jun 13, 2001 at 10:59:00AM +0200, Ken Jones wrote:
>
> NTP takes a while to synchronize once it starts.
--
Robert August Vincent, II (pronounced "bob" or "bob-vee")
[EMAIL PROTECTED], geek@large.
