[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] Revised adaptive-delay code - please test
From: |
Hal Murray |
Subject: |
Re: [gpsd-dev] Revised adaptive-delay code - please test |
Date: |
Tue, 27 Jan 2015 23:46:53 -0800 |
I killed it with buzzkill = False
It took a bit of pounding on the keyboard. I haven't hit it a second time.
Yet.
The 340 (octal) below means it's missed the last 5 polling cycles.
address@hidden work]$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
...
SHM(0) .SHM. 0 l 375 64 340 0.000 -1546.82 1.100
SHM(1) .SHM. 0 l 374 64 340 0.000 -1000.07 0.001
GPSD_JSON(0) .GPSD. 0 l 374 64 340 0.000 -1000.07 16.001
SHM(2) .SHM. 0 l 373 64 340 0.000 223.782 1.072
SHM(3) .SHM. 0 l - 64 0 0.000 0.000 0.000
GPSD_JSON(1) .GPSD. 0 l 371 64 340 0.000 -416.257 1.176
address@hidden work]$
If you look closely, you will notice that the leap-second bug has returned.
:) It started at midnight UTC. (That's a GPS-device bug, not a problem with
gpsd.)
--
These are my opinions. I hate spam.
- [gpsd-dev] Revised adaptive-delay code - please test, Eric S. Raymond, 2015/01/27
- Re: [gpsd-dev] Revised adaptive-delay code - please test, Gary E. Miller, 2015/01/28
- Re: [gpsd-dev] Revised adaptive-delay code - please test, Eric S. Raymond, 2015/01/28
- Re: [gpsd-dev] Revised adaptive-delay code - please test, Gary E. Miller, 2015/01/28
- Re: [gpsd-dev] Revised adaptive-delay code - please test, Eric S. Raymond, 2015/01/28