Yo Hal!
On Thu, 26 Jan 2017 22:24:48 -0800
Hal Murray wrote:
> > And no need to test thos things every build.
>
> Can you test them on a few of the less busy bots?
buildbot is not very smart. I have no idea how to do that.
RGDS
GARY
> And no need to test thos things every build.
Can you test them on a few of the less busy bots?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Yo Hal!
On Thu, 26 Jan 2017 12:28:44 -0800
Hal Murray wrote:
> > Right now, except for known problem children (Solaris, ARM cross
> > compile, etc.) buildbot is all green.
>
> But it didn't catch a batch of problems.
Yup, nor can it be expected to.
> > buildbot
> Right now, except for known problem children (Solaris, ARM cross compile,
> etc.) buildbot is all green.
But it didn't catch a batch of problems.
> buildbot only builds two configurations. One default with no refclocks.
> One default with all refclocks.
> No overhead left to do generic
Yo Hal!
On Thu, 26 Jan 2017 11:29:17 -0800
Hal Murray wrote:
> > Check out the M.2 standard. PCIe + USB on one connector:
>
> Is that PCIe + USB or PCIe or USB?
It is PCIe and USB, at the same time, on the same connector. M.2
is weird, it has a ton of key options,
On Wed, Jan 25, 2017 at 11:47:01PM -0800, Hal Murray wrote:
>
> [From gitlab]
> > It uses SHA1 but not SHA0 - SHA1 is an option for packet MACs. There should
> > be no problem with using the ISC version unconditionally.
https://docs.ntpsec.org/latest/ntpq.html's keytype lists "SHA". Does that
> On Jan 26, 2017, at 2:29 PM, Hal Murray wrote:
>
>> Check out the M.2 standard. PCIe + USB on one connector:
>
> Is that PCIe + USB or PCIe or USB?
>
It can be any of those configurations. Depends on the hardware manufacturers
(slot & module) implementation.
Yo Hal!
On Wed, 25 Jan 2017 23:47:01 -0800
Hal Murray wrote:
> [From gitlab]
> > It uses SHA1 but not SHA0 - SHA1 is an option for packet MACs.
> > There should be no problem with using the ISC version
> > unconditionally.
>
> I though I saw something about getting
Yo Hal!
On Thu, 26 Jan 2017 01:44:22 -0800
Hal Murray wrote:
> With configure --enable-leap-smear
> it gets several warnings, then crashes with:
> [104/105] Linking build/main/ntpd/ntpd
> ntpd/ntp_timer.c.3.o: In function `check_leapsec':
>
> Check out the M.2 standard. PCIe + USB on one connector:
Is that PCIe + USB or PCIe or USB?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Yo Achim!
On Thu, 26 Jan 2017 19:30:12 +0100
Achim Gratz wrote:
> If you had a non-quantized signal to start with you wouldn't need to
> add noise in the first place.
In the digital world all measurements are quantized. All you can do is
make the quant really small.
RGDS
Kurt Roeckx writes:
> On Tue, Jan 24, 2017 at 10:38:50PM +0100, Achim Gratz wrote:
>> sys_fuzz (which whitens the quantization noise on the clock reading)
>> doesn't make a difference or you might not. But presumably Dave Mills
>> didn't put it in there just because he was trying to add useless
An Intel Haswell E3-1225v3 w/ Intel GbE:
[0.00] clocksource: refined-jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 7645519600211568 ns
[0.00] clocksource: hpet: mask: 0x max_cycles: 0x,
max_idle_ns: 133484882848 ns
[0.00] hpet clockevent
With configure --enable-leap-smear
it gets several warnings, then crashes with:
[104/105] Linking build/main/ntpd/ntpd
ntpd/ntp_timer.c.3.o: In function `check_leapsec':
ntp_timer.c:(.text+0x989): undefined reference to `DTOLFP'
collect2: error: ld returned 1 exit status
With configure
14 matches
Mail list logo