On Fri, 31 May 2002 17:26:36 -0700 "Kevin O'Gorman" <[EMAIL PROTECTED]> wrote:
> I configure NTP once every several years, so I cannot usually > remember what's what. > > I've got a server that's been running NTP happily for years, > seems to stay current, and I'm not going to mess with it. > > I've got another machine, glynnis, running RH7.1, and it has the NTP > software, but I cannot get it to synchronize with my server. > I've looked at my firewall rules, and it seems I have all traffic > allowed between these machines, on local-only subnet: 192.168.1.0/24. Just in case, port 123 is open for tcp and udp traffic, correct, although I note from the docs that it only uses udp. > > NTP comes up on glynnis okay, but whenever I run 'ntpq -p' I get > this, which tells me btrixie isn't being used, and that the > local clock is being taken as the time source: (btrixie is an > entry in my /etc/hosts file, equated to 192.168.1.148) > > [root@glynnis init.d]# ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > btrixie 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00 > LOCAL(0) LOCAL(0) 10 u - 64 0 0.000 0.000 4000.00 Are you sure that glynnis can reach btrixie? > My configuration file is very simple. > > > server 192.168.1.148 > > > > server 127.127.1.0 # local clock > > fudge 127.127.1.0 stratum 10 > > > > driftfile /etc/ntp/drift > > multicastclient # listen on default 224.0.1.1 > > broadcastdelay 0.008 > > > > authenticate no Kurt -- Your lucky number has been disconnected. _______________________________________________ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
