Configure NTP - should be a snap, but it isn't

Kevin O'Gorman kevin
Mon May 17 11:32:23 PDT 2004


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.

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 at 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

*********

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


Anybody have a clue?

++ kevin




-- 
Kevin O'Gorman  (805) 650-6274  mailto:kevin at kosmanor.com
Permanent e-mail forwarder:  mailto:Kevin.O'Gorman.64 at Alum.Dartmouth.org
At school: mailto:kogorman at cs.ucsb.edu
Web: http://www.cs.ucsb.edu/~kogorman/index.html
Web: http://kosmanor.com/~kevin/index.html

"Life is short; eat dessert first!"



More information about the Linux-users mailing list