Actually, I don't know if you checked my output, but I had already tried
ntpdate.
The two machines before attempting to do ntpdate (I always try ntpdate first
before launching ntpd) were about 23 seconds apart (not really all that far
apart IMHO) I am trying that other date/time package (clockspeed) now to
see if I can get the systems synced up.
I still don't know why ntpdate was giving me a:
12 Jun 14:54:30 ntpdate[26233]: no server suitable for synchronization found
when I would feed it the server by name and by ip address.
-Tony
----- Original Message -----
From: Robert August Vincent II <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, June 13, 2001 8:10 AM
Subject: Re: Help! NTP gurus needed...
> 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.
>
>
