On Mon, 2006-10-23 at 06:19 +1300, Rob Brown-Bayliss wrote: > [root@localhost ~]# ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > mu-relay1.masse 192.5.41.40 2 u 16 64 177 170.570 -798.72 12760.3 > ns1.compass.net 128.250.36.3 2 u 14 64 177 112.739 -13008. 7668.06 > cobol.appello.n 128.250.37.2 2 u 14 64 177 162.234 -897.55 11922.0 > ntp.thistledown .GPS. 1 u 19 64 177 203.800 -3927.4 9253.24 > gen2.ihug.co.nz 130.217.76.49 2 u 14 64 177 140.795 -7057.9 7349.37 > > [root@localhost ~]# ntpdate > 23 Oct 06:15:35 ntpdate[3869]: no servers can be used, exiting I see the same sort of thing. I'm hazarding a guess that ntpdate is trying to find servers from a different place than the NTP daemon looks. Very briefly looking at the ntpdate man file, I think you're supposed to specify a server with the ntpdate command, I don't think it looks for servers in a configuration file. > One thing I have noticed is the reach value is different every time I > run ntpq. Does it change when you've left NTP running for a while? I've just rebooted, and mine started at 77, went up to 177 after the poll period, then to 377 after the next poll period. Do ntpq -p a few times, and watch the "when" and "poll" columns over a few seconds. See the when counting up? (In seconds.) Once the when count has counted up to the value in the poll period (e.g. if it's currently polling every 64 seconds, you'll see the when count, count up to 64, then restart counting up), it'll poll the servers and adjust the local NTP daemon. You should see the reach column increase after a little while. -- (Currently testing FC5, but still running FC4, if that's important.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
