Re: Something broken with minpoll/maxpoll

g...@rellim.com said: > But this bug only showed up after running for a while, so we'd need a > synthetic run environment too. ntpq cv xxx gives you lots of info for a refclock. (get the xxx from apeers) It doesn't include minpoll/maxpoll, but that could be fixed. I think TESTFRAME will be a

Re: Something broken with minpoll/maxpoll

> How to add regression tests for such config options? Part of that might be possible with a variant of ntpq. The idea would be to only print the stuff that should be constant, save it to a file, and compare that with last known good. -- These are my opinions. I hate spam.

We should put the notrap keyword back in

and ignore it to maximize backward compatibility. The idea is to let people who want to try ntpsec run with their old ntp.conf I think the current code ignores the rest of the line. That's not what we want. -- These are my opinions. I hate spam.

Re: Something broken with minpoll/maxpoll

Yo Hal! On Sat, 24 Sep 2016 13:30:29 -0700 Hal Murray wrote: > Some of my PPS refclocks are now ramping up the poll interval. > I think there used to be some code that set maxpoll to minpoll for > refclocks. Did you break that? Fix pushed. Please test. An undefined

Re: ✘minpoll=maxpoll from 0 to 8 for RasPi 3

Yo All! Since minpoll=maxpoll=0 is starting to work, I added another test on the RasPi 3 for that value. No need to do so on the Xeon since that would clearly be a bad setting. RasPi3: Local Clock Local Clock Local ClockPPS PPS Poll Freq Offset 90% Jitter 90%

Re: How does ^C work in Python?

In Python, there's a minimal generic interrupt handler which calls Py_AddPendingCall() to schedule a call to a more complete handler. The main interpreter loop then calls Py_MakePendingCalls() every few iterations or on return from any system call. The default behavior for handling SIGINT is to

Re: Warnings from FreeBSD 12 on Raspberry Pi 2

Hal Murray : > Is there an obvious way to fix this stuff? > > ../../tests/libntp/timespecops.c:112:103: warning: format specifies type > 'long' but the argument has type 'time_t' (aka 'long long') [-Wformat] > ../../tests/libntp/timespecops.c:112:124: warning: format

Warnings from FreeBSD 12 on Raspberry Pi 2

Is there an obvious way to fix this stuff? ../../tests/libntp/timespecops.c:112:103: warning: format specifies type 'long' but the argument has type 'time_t' (aka 'long long') [-Wformat] ../../tests/libntp/timespecops.c:112:124: warning: format specifies type 'long' but the argument has type