I had cause to look at tinker huffpuff recently and a number of things
concern me.
1) It is applied globally, and that seems to include reference clocks,
including the local clock (which you can expect to find on most real
world configurations, even though it is often inappropriate for them).
David,
The huff-'n-puff scheme was never intended to be universally applicable.
It is intended for the poor bloke with an overloaded DSL line to an ISP
and very little else. It could be further engineered as you propose and
others are welcome to do that. You should understand that would be a
d
David L. Mills wrote:
>
> The huff-'n-puff scheme was never intended to be universally applicable.
> It is intended for the poor bloke with an overloaded DSL line to an ISP
> and very little else. It could be further engineered as you propose and
Where I work falls into that category (2 Mb/s S
http://support.ntp.org/bin/view/Dev/NewNtpConfFormat#Individual_huff_n_puff_buffers_f
has been on the "good idea list" for a while.
--
Harlan Stenn <[EMAIL PROTECTED]>
http://ntpforum.isc.org - be a member!
___
questions mailing list
questions@lists.n
David,
See the Association Management page, Orphan Mode section. It would be
odd if the casual reader did not come away from that section with the
impression that orphan mode was always preferred over the local clock
driver.
What you report seems to be common practice in packaged systems -
in
Harlan,
It's not as simple as you think. In fact, it's not as simple as I
thought. The scheme is a maximim a-posteriori (MAP) statisical
estimation method. The estimator thinks it has a good measure of the
correct value and then collects samples that reinforce that value.
The trick is to relia
"David L. Mills" <[EMAIL PROTECTED]> writes:
>David,
>See the Association Management page, Orphan Mode section. It would be
>odd if the casual reader did not come away from that section with the
>impression that orphan mode was always preferred over the local clock
>driver.
>What you report s
David L. Mills wrote:
>
> See the Association Management page, Orphan Mode section. It would be
> odd if the casual reader did not come away from that section with the
The casual reader wouldn't get to that section. They would stop at the
Automatic NTP Configuration Options page, where the on
David,
You have a very good point. Orphan mode has been around for more than a
year and has been carefully described in the online documentation and
snapshots. Users of the release version, which is a cherrypicked but
incomplete extract of various fixes and improvements over the year, may
have
"Unruh" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> "David L. Mills" <[EMAIL PROTECTED]> writes:
[...]
>> What you report seems to be common practice in packaged systems -
>> include the local clock driver - is unfortunate. I consider that a bad
>> practice, but then my engineerin
10 matches
Mail list logo
