On 10/7/06, Henning Brauer <[EMAIL PROTECTED]> wrote:
> <inserts USB GPS device>
> uplcom0 at uhub1 port 4
> uplcom0: Prolific Technology PL2303 Serial, rev 1.10/2.02, addr 4
> ucom0 at uplcom0
> # nmeaattach cuaU0
> # sysctl hw.sensors.30
> hw.sensors.30=nmea0, GPS, 0.77 secs, OK, Fri Oct 6 21:23:53.453
> # echo 'sensor nmea0' > /etc/ntpd.conf
> # date
> Fri Oct 6 21:29:29 EDT 2006
> # date 35
> Fri Oct 6 21:35:00 EDT 2006
> # sysctl hw.sensors.30
> hw.sensors.30=nmea0, GPS, 281.16 secs, OK, Fri Oct 6 21:35:28.815
> # ntpd -ds
> ntp engine ready
> sensor nmea0 added
> sensor nmea0: offset -280.827497
> no reply received in time, skipping initial time setting
> sensor nmea0: offset -280.817099
> sensor nmea0: offset -280.817388
> sensor nmea0: offset -280.841698
> sensor nmea0: offset -280.843981
> sensor nmea0: offset -280.829276
> sensor nmea0: offset -280.840579
> <snip>
> This goes on forever and the time is never actually adjusted according
> to the timedelta. The timedelta seems to be working quite well, but
> ntpd isn't adjusting according to it. What am I doing wrong?
you never get a "adjusting local clock by ..." message?!?
Correct. I just keep getting this message forever: "sensor nmea0:
offset -280.800595". My ntpd.conf has no servers defined in it it only
has this one sensor. I ran it for a few hours and it never adjusted my
time at all (no messages in /var/log/daemon either about it adjusting
either. I'm running a box a week or so away from -current and it
doesn't seem like any of that code has been touched in a while.
# uname -a
[EMAIL PROTECTED]:6$ uname -a
OpenBSD pi.local 4.0 GENERIC#3 i386
Any ideas...?
-Sam
