Eric S. Raymond esr at thyrsus.com :
>Gary E. Miller via devel :
>> > So there is nothing you recommend be merged at this time?
>>
>> I sorta wish NTPsec had a staging area like the Linux kernel does.
>>
>> There is value to a small and clean u-blox driver fully integrated
>> into NTPsec. But wi
I have logs going back to 2019-10-26. These clock fuzz errors started on
ntp1 on 2019-11-02 and ntp2 on 2019-11-21.
On 2019-11-02, I upgraded to NTPsec 1.1.7 (from 1.1.3) and enabled NTS
(as both a client and server).
On 2019-11-08, I added the GPS to ntp2. Based on the dates, that seems
unrelate
/me gets popcorn, sits back:-)
--
Sanjeev Gupta
+65 98551208 http://www.linkedin.com/in/ghane
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On 11/25/19 6:29 PM, James Browning via devel wrote:
> The suggested
> means of connecting to a local GPSD instance is to use the gpsd refclock.
That's the opposite of my understanding. See:
https://lists.ntpsec.org/pipermail/devel/2016-October/002392.html
and also make sure to read this:
https://
Gary E. Miller via devel :
> > So there is nothing you recommend be merged at this time?
>
> I sorta wish NTPsec had a staging area like the Linux kernel does.
>
> There is value to a small and clean u-blox driver fully integrated
> into NTPsec. But without KPPS it is inferior at timekeeping.
>
Yo Sanjeev!
On Tue, 26 Nov 2019 07:15:30 +0800
Sanjeev Gupta via devel wrote:
> The _GPSD_ man page suggests setting minpoll and maxpoll to 4.
I can find no such statement. Can you locate that for me?
gpsd-time-service-howto.html says:
"ntpd seems to better use a PPS refclock when the po
Yo James!
On Mon, 25 Nov 2019 16:29:29 -0800
James Browning via devel wrote:
> the SHM refclock driver lacks a mechanism to correlate
> PPS information with the data stream
Huh? Wrong.
RGDS
GARY
---
Gary E. Miller Rellim
Yo Richard!
On Fri, 22 Nov 2019 23:09:17 -0600
Richard Laager via devel wrote:
> The NTPviz output says, "TDOP is a dimensionless error factor. TDOP
> ranges from 1 to greater than 20. 1 denotes the highest possible
> confidence level. 2 to 5 is good."
>
> I routinely have TDOP values below 1,
On Mon, Nov 25, 2019 at 3:15 PM Sanjeev Gupta via devel
wrote:
> From: docs/driver_shm.adoc
>
> Is the first paragraph still required, if it doesn't apply to current
> nrpsec?
>
> And I cant parse the second paragraph, especially the first line. What
> should I use? Not the ancient method, sure
From: docs/driver_shm.adoc
Is the first paragraph still required, if it doesn't apply to current
nrpsec?
And I cant parse the second paragraph, especially the first line. What
should I use? Not the ancient method, surely?
The _GPSD_ man page suggests setting minpoll and maxpoll to 4. That was
Gary E. Miller via devel writes:
> If the guy that wrote it wanted to work on it under the NTPsec umbrella
> that would be good. A little guidance and the guy that wrote that could
> be very useful to NTPsec.
"The guy that wrote" it has last participated on this list over a year
ago in this very
Yo Eric!
On Mon, 25 Nov 2019 08:18:21 -0500
"Eric S. Raymond" wrote:
> Gary E. Miller via devel :
> > I just took a quick look at refclock_ubx.c
> >
> > An interesting start, [...]
> So there is nothing you recommend be merged at this time?
I sorta wish NTPsec had a staging area like the Linu
Richard Laager via devel writes:
> These both have the following CPU (which is older):
> Intel(R) Xeon(R) CPU X5460 @ 3.16GHz
These may not yet have consistent TSC between cores/sockets (or require
BIOS tweaks for that). The other result where you show that
MONOTONIC_RAW reads much slo
Hal Murray :
>
> >From devel/hacking:
>
> Only POSIX-1.2001/SUSv3 library functions should be used (a few
> specific exceptions are noted below). If a library
> function not in that standard is required, then a wrapper function for
> backward
> compatibility must be provided. One notable case
Mark Atwood via devel :
> On Sun, Nov 24, 2019, at 19:32, Hal Murray via devel wrote:
> >
> > e...@thyrsus.com said:
> > > If we don't see any evidence of beat-induced quantization, I'm willing to
> > > say
> > > we drop this code.
> >
> > How about adding a --disable-fuzz configure option so w
Gary E. Miller via devel :
> Is there an existing patch to remove the fuzzing?
There is not. See my reply to Mark.
--
http://www.catb.org/~esr/";>Eric S. Raymond
signature.asc
Description: PGP signature
___
devel mailing list
devel@n
Gary E. Miller via devel :
> I just took a quick look at refclock_ubx.c
>
> An interesting start, but followup messsages today on the list are
> assuming this driver does things that it does not do.
>
> 1) It does not, ever, config the u-blox. It does not, ever, write to
> the u-blox to query it
>From devel/hacking:
Only POSIX-1.2001/SUSv3 library functions should be used (a few
specific exceptions are noted below). If a library
function not in that standard is required, then a wrapper function for backward
compatibility must be provided. One notable case is clock_gettime()
which is u
18 matches
Mail list logo
