ed to make sure it works for the 8250-based UART in my box,
YMMV, apologies in advance that email will almost certainly break lines in it. Its really much more trivial than you
were thinking :)
Matt
commit 85aa50c40dae86b2d5051902e72fc1b18c1c8563
Author: Matt Corallo
Date: Sun Sep 27 23:02:24
I was wondering about this too, so sat down and patched kernel to pull timestamps right after the interrupt fires and
then decide later if it was because of DCD change (passing the timestamp through the dcd_change callback, its a pretty
trivial patch). It cut the jitter down some (a few us, maybe
NTPSec's ntpviz seems to be happy eating output from ntpd's peer/loopstats logs and generates pretty graphs with python
and rrdtool.
Matt
On 9/16/20 2:12 PM, Rob van der Putten wrote:
Hi there
On 23/08/2020 14:10, Uwe Klein wrote:
Anybody else getting "request received" from TheFork
and
It looks like the ML's SpamAssassin is confiugred with at least one DNSBL which stopped working in 2015 (and now returns
true for everything - DNS_FROM_AHBL_RHSBL) and probably a few more per the wiki.
More importantly, there seems to be at least 5 folks who managed to register a ticket system t
Also, while I'm on the subject, what about multiple "prefer" peers? I've seen several folks indicate that they have "two
GPS receivers" or the like, but there doesn't seem to be a good way to configure ntpd for that use-case.
Matt
On 9/15/20 12:26 PM, Matt C
Is there any interest in a patch to select across multiple PPS lines (maybe median of the available lines, or maybe
using clock_combine) instead of just blindly taking the first one? This would also allow us to take the second available
PPS line if the first one fails the "within 400ms" requireme
