> Hal Murray writes:
> no-...@no-place.org writes:
[Cross-posting to news:free.comp.dns.]
>> I am trying to get to know SNTP by doing some Winsock programming.
>> In particular, I am using
>> getaddrinfo("pool.ntp.org", "123", &hints, &gaires);
>> where hints has been set u
> David Woolley writes:
[Cross-posting, and setting Followup-To:, to news:comp.dsp.]
[...]
> In Fourier terms, the spectral width of a piano note is going to be
> more than 12ppm and depend on the exact interval over which you
> measure it. I would also suspect that the zero cro
Hal Murray wrote:
It effectively does imply 'preempt', since a pool of servers (from a
pool xyz statement) will be monitored and regularly filtered, replacing
the worst servers with the results of a fresh dns lookup.
Does it replace bad servers or only dead ones?
I think the latter, but I ha
I've been informed by the folks with the ability to do a laying-on of
hands with this system have run an experiement where they disabled NTP
and indeed no longer see the 600 millisecond time shifts.
If there are indeed somewhat common 600 millisecond time steps,
doesn't that suggest that NTP is ha
unruh wrote:
> sntp uses the same round trip algorithm that ntp does.
If he writes his implementation similar to ntp.org's reference
implementation, or even similar to the RFC reference standard.
I've seen many things use NTP protocol to request and parse
a timestamp packet from a NTP server,
On Thu, 07 Feb 2013 08:10:44 +, David Woolley
wrote:
> If it is measuring the
>frequency, the first problem is going to be defining what you mean by
>frequency. In Fourier terms, the spectral width of a piano note is
>going to be more than 12ppm and depend on the exact interval over which
Mike S wrote:
On 2/7/2013 2:17 AM, Terje Mathisen wrote:
Most (GSM/3G/4G) cell towers make do with OCXOs/TCXOs, but very good
ones, rated at a few ppb/day in drift rate.
...
The interesting part here is that the actual requirement is for
_frequency_ synchronization, not absolute time sync!
On 2/7/2013 2:17 AM, Terje Mathisen wrote:
Most (GSM/3G/4G) cell towers make do with OCXOs/TCXOs, but very good
ones, rated at a few ppb/day in drift rate.
...
The interesting part here is that the actual requirement is for
_frequency_ synchronization, not absolute time sync!
You're probabl
Have you ever tried to synchronize to the pool servers with NTPD for any
length of time? I did once, admittedly several years ago. They weaved
and waved all over the time domain so much (at least +- 50 ms) that it
was impossible to have stable time on the client. I would suggest you
try
Robert Scott wrote:
As I explained in another thread last week, my app is not a time app.
It is a precision audio frequency measuring app. The users of this
app expect frequency accuracy on the order of 12 ppm. To achieve this
I had previously assumed this was an electronic tuning fork, gen
10 matches
Mail list logo
