On Wed, 2004-03-03 at 18:29, Kaj J. Niemi wrote: > You've got three server definitions but only one of them is relaxed. What > does "ntpq -np" (or "ntpq -n -c peers") tell you? If all you get back is > "connection refused" ntpd isn't running which usually means that the amount > of time needed to be synchronised is more than the limit (1000 s, iirc). On > the other hand if you get something like the example below, you've got timing > from two servers while the third is somewhere in the void. > > % ntpq -np > remote refid st t when poll reach delay offset jitter > ============================================================================== > 212.226.226.1 .INIT. 16 u - 1024 0 0.000 0.000 4000.00 > *192.26.119.7 192.36.144.23 2 u 465 512 377 7.779 11.173 0.810 > +192.26.119.4 192.36.144.22 2 u 482 512 377 9.948 8.984 1.891 > It looks like my output is *all* in the void - all three lines come back as your first. > If you're concerned of getting the correct time on boot, you should > put the IP addresses of your time servers (one per line) in > /etc/ntp/step-tickers. > > In /etc/ntp.conf the "netmask 255.255.255.255" statements are redundant, > "restrict 69.22.157.240 nomodify notrap noquery" should be the equivalent. > > Are you using a firewall? The ntpd startup script attempts to punch holes > into RH-Lokkit-0-50-INPUT but that'll only work if the said chain is being > referenced in INPUT. /sbin/service iptables status should be your friend in > this case. > > Hth. > > > // kaj While I've had iptables running, stopping it has no effect. Thanks for the help and info, though. -Don
