Hi,
I wanted to try using a timedelta sensor for openntpd (on OpenBSD
4.0-release with errata patches) but don't seem to have that much luck
with it.
The sensor (Gude ADS Expert mouseClock USB, rev 1.10/1.00, addr 2) as
such seems to work fine :
hw.sensors.11=udcf0, DCF77, 0.34 secs, OK, Wed Nov 15 18:34:56.044
/var/log/daemon only shows :
Nov 15 15:02:14 montecristo ntpd[18634]: listening on 10.0.16.1
Nov 15 15:02:14 montecristo ntpd[18634]: listening on 10.0.22.1
Nov 15 15:02:14 montecristo ntpd[18634]: ntp engine ready
It never shows any clock synced message, which apparently is also
confirmed by the clients :
Nov 15 15:14:13 cohiba ntpd[30901]: reply from 10.0.16.1: not synced,
next query 3197s
Nov 15 16:07:30 cohiba ntpd[30901]: reply from 10.0.16.1: not synced,
next query 3135s
Nov 15 16:59:45 cohiba ntpd[30901]: reply from 10.0.16.1: not synced,
next query 3158s
Also the drift file remains at the last value from when I switched from
stratum II servers to this timedelta sensor.
the /etc/ntpd.conf simply lists :
# $OpenBSD: ntpd.conf,v 1.7 2004/07/20 17:38:35 henning Exp $
# sample ntpd configuration file, see ntpd.conf(5)
# Addresses to listen on (ntpd does not listen by default)
listen on 10.0.16.1
listen on 10.0.22.1
# timedelta sensor
sensor udcf0
And if I finally run ntpd -d the output I get is :
listening on 10.0.16.1
listening on 10.0.22.1
ntp engine ready
sensor udcf0 added
sensor udcf0: offset -0.337391
sensor udcf0: offset -0.337878
sensor udcf0: offset -0.338369
sensor udcf0: offset -0.348855
sensor udcf0: offset -0.339345
Can anyone be so kind to advice me ?
Kind Regards,
Joris Van Herzele
