ntpd configuration . . . and errors

[Bill Moran]

On Fri, 14 Jul 2006 17:25:52 +0100 (BST)
Owen G <owen_pg at yahoo.com> wrote:

[snip]

> Then I corrected this "run once and quit option" and now get no
> "errors" on the console anymore and "ntpq -p" gives:
> 
> epia# ntpq -p
>      remote           refid      st t when poll reach   delay   offset 
> jitter
> ==============================================================================
> *h2348.serverkom 192.53.103.108   2 u   62  128  377   63.394    9.194 
> 19.331
> epia#
> 
> BTW, The idea of using "europe.pool.ntp.org" as the only server was
> that the address itself resolves to a round robin pool of servers -
> obviating the need for multiple entries.  I will of course sit
> corrected.
> 
> My concern is now that ntpd doesn't seem to report that it has checked
> the time with any timesource.  Any ideas how to confirm (apart from
> changing the time to something wrong but only wrong by less than 1000
> seconds?)

ntpd will log time changes to syslog.

On every system I've seen, they end up in /var/log/messages.

Note that ntpd is rather conservative.  It might spend 30 minutes checking
and rechecking the time before it decides to make an adjustment.  Let it
run for a day and check tomorrow to see if it's making changes.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com