From: "Gilbert Sebenste" <sebenste@xxxxxxxxxxxxxxxxxxxxxx>
> On Mon, 12 Apr 2004, Gilbert Sebenste wrote:
>
> >
> > I need to be clearer here. The primary machine in my office needs to be
a
> > time server, so that the other machines can use the sync program and
> > "ping" to get the correct time from the primary machine. That is to say,
> > it should not only be running NTP, but the other office machines should
be
> > able to get the correct time from it using the Redhat time "Date/Time
> > properties" little program. It has a message on there that says "Enable
> > Network Time Protocol", and then I use that to (try) to sync with my
> > primary office machine. but the primary office machine refuses to accept
> > it. I just use ntpdate via command mode to see if it is actually working
> > properly from another machine.
>
> Well, guess what. It just started working. From my other machines, I can
> now use the RedHat NTP server to get the correct time from my master
> machine. Ntpdate stil won't work, but that's OK...as long as this works,
> I'm happy. I just don't know how it happened.
>
> Weird.
Not weird. It takes awhile before ntpd is satisfied it has an accurate
enough time to be used as a basis for the other systems. This may be as
much as half an hour, at which time it is remarkably accurate.
{^_^}
