Gary E. Miller via devel writes:
> There is a gpsd program in the contrib/ directory. It tests your
> CPU granularity. On a Raspberry Pi that is about 52 ns. Worse
> on an Intel chip.
The actual granularity on RasPi can't be better than 52ns (the clock
it's based on is 19.2MHz) and you can dete
On 11/23/19 3:02 AM, Hal Murray wrote:
> The code that reads the clocks works hard to make sure that fuzzing the
> bottom
> bits doesn't make time go backwards. That logging is what happens when
> things
> go wrong.
>
> What sort of hardware/OS are you running on?
2x Intel Xeon CPU X5460 @ 3
On 11/23/19 8:19 PM, Gary E. Miller via devel wrote:
> There is a gpsd program in the contrib/ directory. It tests your
> CPU granularity. On a Raspberry Pi that is about 52 ns. Worse
> on an Intel chip.
It looks like you're talking about clock_test.c. I grabbed the version
from gpsd git:
https
We don't have a policy against 3p Python modules.
On the other hand, I'm not a fan of importing the entire cheese shop.
On the other other hand, I usually pull in the gpsd Python module on machines
I'm running ntpd on.
On the other other other hand, can we have a Python binding on the C crypto
ro
Yo Richard!
On Sat, 23 Nov 2019 01:53:33 -0600
Richard Laager via devel wrote:
> That trade-off makes sense to me. But, of the two, it seems like
> following the PPS closely is what I'd want. The PPS is supposed to be
> more accurate than my computer.
There is a gpsd program in the contrib/ dir
Yo Richard!
On Sat, 23 Nov 2019 02:09:37 -0600
Richard Laager via devel wrote:
> On 11/13/19 1:43 PM, Gary E. Miller via devel wrote:
> > A simple u-blox
> > NEO-M8N for $10 will do. Then $5 for a TTL to RS-232 converter.
> >
> > Get one of these NEO-M8N for $7:
> >
> > https://www.ebay.com/i
[Hal, I've asked before, but again: Can you please configure whatever
you use as your mailer to not always break threading when you reply?]
Hal Murray via devel writes:
> The code that reads the clocks works hard to make sure that fuzzing the
> bottom
> bits doesn't make time go backwards. T
Richard Laager via devel writes:
> These aren't actually NEO-M8N. Are you saying that these ATGM336H-5N are
> good enough?
If you want to build up multiple GPS receivers the best deal available
is still this:
http://navspark.mybigcommerce.com/navspark-mini-6pcs-pack/
With the accompanying patch
Also, what does this mean and is it a problem (it's an ERR level)? I'm
seeing it on both servers.
2019-11-23T01:49:33.497786-06:00 ntp1 ntpd[28568]: CLOCK: ts_prev 1574495373 s
+ 497394102 ns, ts_min 1574495373 s + 497388500 ns
2019-11-23T01:49:33.497936-06:00 ntp1 ntpd[28568]: CLOCK: ts 15744953
The JUNK stuff is a packet that looks like a NTP packet but the extension
doesn't make sense. I haven't figured out what generates them. They should
be rate limited. We should add figuring out what they are to the
get-ready-for-a-release list.
Yes, there is a lot of NTS clutter in the log fi
On 11/13/19 1:43 PM, Gary E. Miller via devel wrote:
> A simple u-blox
> NEO-M8N for $10 will do. Then $5 for a TTL to RS-232 converter.
>
> Get one of these NEO-M8N for $7:
>
> https://www.ebay.com/itm/Replacement-NEO-M8N-GPS-BDS-Dual-mode-Module-Flight-Control-Satellite-ATGM336H/182622902135
Also, what does this mean and is it a problem (it's an ERR level)? I'm
seeing it on both servers.
2019-11-23T01:49:33.497786-06:00 ntp1 ntpd[28568]: CLOCK: ts_prev 1574495373 s
+ 497394102 ns, ts_min 1574495373 s + 497388500 ns
2019-11-23T01:49:33.497936-06:00 ntp1 ntpd[28568]: CLOCK: ts 15744953
This is probably a question for Hal:
I'm getting a lot of useless-to-me NTS log messages. I assume these are
just random things scanning open ports. I wonder if these should be
toned-down from ERR to DEBUG.
2019-11-23T01:56:32.467297-06:00 ntp2 ntpd[16212]: NTSs: TCP accept-ed from
23.91.196.81:
13 matches
Mail list logo
