We have two copies of the documentation for the statistics files. One in
docs/includes/mon-commands.txt and another in docs/statfiles.txt
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailm
Thanks.
f...@fwright.net said:
> That seems inconsistent with the following comment in arch/powerpc/kernel/
> time.c:
> * TODO (not necessarily in this file):
> * - improve precision and reproducibility of timebase frequency
> * measurement at boot time.
I didn't see any calibration code, bu
Yo Hal!
On Sat, 04 Feb 2017 17:19:21 -0800
Hal Murray wrote:
> g...@rellim.com said:
> > Then you have to take aging into account. A 10 year old Mac may
> > have difted a lot. Or maybe the crystal got bumped.
>
> > Also a lot of crystals are now surface mount. The soldering
> > process may
g...@rellim.com said:
> Then you have to take aging into account. A 10 year old Mac may have difted
> a lot. Or maybe the crystal got bumped.
> Also a lot of crystals are now surface mount. The soldering process may
> have bend to crystal a lot.
Do you have references to any published data?
Yo Fred!
On Sat, 4 Feb 2017 16:19:00 -0800 (PST)
Fred Wright wrote:
> When you think about it, the manufacturer knows perfectly well the
> nominal frequency of the crystal being stuffed, and is also
> programming onboard nonvolatile memory (typically EEPROM) with
> various parameters,
I used to
On Tue, 31 Jan 2017, Hal Murray wrote:
> b...@kernel.crashing.org said:
> > Right, we just use the value provided by Open Firmware. Any chance you can
That seems inconsistent with the following comment in
arch/powerpc/kernel/time.c:
* TODO (not necessarily in this file):
* - improve precision
strom...@nexgo.de said:
> I don't know how compatible you are trying to stay with the "classic"
> output, but to me it seems you'd be better off with such changes made
> conditional on the use of an option, either a new one or maybe the existing
> '-W' one (which means that the extra space first g
> Is the jitter column header/data supposed to have moved 1 character to the
> right?
Yes. The printout is now 79 characters wide rather than 78.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.
After a git pull waf / autorevision don't seem to be recognizing that
the version files should be regenerated. I've removed
wafhelpers/.autorevision to trigger a rebuild manually, but it seems
like a bug in the buildsystem.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Bl
Hal Murray writes:
> I just pushed a fix. Please test.
>
> I bumped the width from 78 to 79. If that screws up, we should document a
> test case. I'm assuming the output supports an 80 character line.
I don't know how compatible you are trying to stay with the "classic"
output, but to me it se
On Sat, Feb 04, 2017 at 01:39:45AM -0800, Hal Murray wrote:
> Good catch. Thanks.
>
> I just pushed a fix. It's the sort of kludge that Eric won't like but I
> don't have a better idea.
Hey Hal,
Looks better.
$ ntpq -pn ; ./ntpclients/ntpq -pn
remote refid st t when pol
Hal Murray :
>
> matthew.sel...@twosigma.com said:
> > We need some backwards compatibility for ntp classic servers. Eg, the
> > server has only microsecond precision. We need to avoid adding trailing
> > zeros that are not actually significant.
>
> Good catch. Thanks.
>
> I just pushed a fi
matthew.sel...@twosigma.com said:
> We need some backwards compatibility for ntp classic servers. Eg, the
> server has only microsecond precision. We need to avoid adding trailing
> zeros that are not actually significant.
Good catch. Thanks.
I just pushed a fix. It's the sort of kludge tha
13 matches
Mail list logo
