Date: Fri, 24 Mar 1995 19:37:15 +0200 From: Mark Murray <mark@grondar.za> To: hackers@FreeBSD.org Subject: XNTPD question. Message-ID: <199503241737.TAA19551@grunt.grondar.za>
next in thread | raw e-mail | index | archive | help
Hi folks
I have set up xntpd on my machine, and for the most part it works very
well. (Thanks!)
Can anyone help with a niggling problem I have?
The _only_ problem I have (and this is with it compiled out-of-the-box with
no crypto code) are the following messages logged at startup, indicating
(?) that the system clock is not goin to be used:
> Mar 19 11:05:03 grunt xntpd[81]: xntpd version=3.4e (beta multicast); Sat Mar 18 21:50:23 SAT 1995 (1)
> Mar 19 11:05:03 grunt xntpd[81]: tickadj = 5, tick = 10000, tvu_maxslew = 495
> Mar 19 11:05:04 grunt xntpd[81]: refclock_newpeer: clock type 1 invalid
> Mar 19 11:05:04 grunt xntpd[81]: configuration of 127.127.1.7 failed
> Mar 19 11:05:04 grunt xntpd[81]: using xntpd phase-lock loop
Here is my /etc/ntp.conf:
# ntp.conf for grondar.za
# Mark Murray, March 1995
#
#
# hardware clocks
#
server 127.127.1.7 # local clock <- Local guru swears this should work
#
# servers and peers
# syntax: {server,peer} addr [ key 1-15 ] [ version 1/2/3 ]
#
server <site-1> version 3 # stratum 3 iafrica
server <site-2> version 3 # stratum 3 iafrica
server <site-3> version 3 # stratum 3 UniNet
#
# listen to broadcasts?
#
broadcastclient yes
broadcastdelay 0.003
#
# authentication stuff
#
keys /etc/ntp.keys
authenticate no
#trustedkey
requestkey 65535
controlkey 65535
authdelay 0.00005 # i486dx/50MHz (+O)
#
# various parameters and files
#
precision -10
driftfile /etc/ntp.drift
monitor yes
--
Mark Murray
46 Harvey Rd, Claremont, Cape Town 7700, South Africa
+27 21 61-3768 GMT+0200
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503241737.TAA19551>