g...@rellim.com said:
> Fix pushed. Please test. An undefined maxpoll is not always set to the
> default maxpoll (NTP_MAXDPOLL). For a local refclock the default max poll
> is the minpoll.
I think it's working correctly. I haven't seen any refclocks ramping up.
--
These are my opinions. I
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 s
Yo Hal!
On Mon, 26 Sep 2016 13:30:25 -0700
Hal Murray wrote:
> > 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 las
> 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.
__
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.
__
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 maxpoll is not always set t
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% Stabili
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 rai
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 specifies type
> 'long' but
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 'ti
10 matches
Mail list logo