ntpd on Red Hat

[kentborg at borg.org (Kent Borg)]

On Thu, Apr 04, 2002 at 11:27:15AM -0500, Jerry Feldman wrote:
> It appears that ntpd is essentially a nop. It is running, but does
> not appear to adjust the time based on the servers. I have the same
> servers set up for my home system (SuSE running xntpd), which does
> appear to time synch successfully.

What do you get from:

  $ /usr/sbin/ntpq -p

Do you get interesting and varying values for "delay", "offset", and
"jitter"?  Are some of your reference servers marked with "*", "+",
and "-"?  Do the values for "reach" have nearly as many 1's set as
does the idea 0x377?  Does "when" increment until it hits the "poll"
value and then update the other values?

If so, then ntpd is getting time information but for some reason isn't
able to set the clock.  If not, then ntpd might be capable of setting
the clock, but isn't getting out to your reference sources.

That might help you split your problem in two.


-kb, the Kent whose ntpd daemon used not to be willing to serve time
(was only willing to be a client) until upgrading to RH 7.2.