>How accurately do you need to do this? Is this a one-off measurement just
>to test the accuracy of the clock on the NI board? Is that a separate
>oscillator, or one driver from one of the computer clock lines? My guess
>is that it will be a separate clock.
It might be running off the PCI cl
Hal Murray wrote:
>> How accurately do you need to do this? Is this a one-off
>> measurement just to test the accuracy of the clock on the NI board?
>> Is that a separate oscillator, or one driver from one of the
>> computer clock lines? My guess is that it will be a separate clock.
>
> It might
David J Taylor wrote:
> Unruh wrote:
> []
>> But ntp arguably should handle jumps in time or frequency faster than
>> the hours or days it takes now.
>
> Why? A jump (to me) implies an error in the hardware. Who is to say that
> it's a one-off jump, or that it might not occur again in a few sec
"David J Taylor" <[EMAIL PROTECTED]> writes:
>Unruh wrote:
>[]
>> But ntp arguably should handle jumps in time or frequency faster than
>> the hours or days it takes now.
>Why? A jump (to me) implies an error in the hardware. Who is to say that
Or an error in software (missed timer ticks), or
Unruh wrote:
[]
>> minutes ot hours? Should it not be the hardware which is corrected,
>> not NTP?
>
> On that argument ntp should not do anything more than rdate did,
> since if
> the oscillator on the clocks were perfect there would be no need for
> anything but an single setting of the clock on
Hal,
You should see the current web documentation on rate control and the KoD
packet. Rate control is on a per-client baiss, so if 10,000 clients all
light up at the same time, each will be treated individually. KoD
packets are themselves rate controlled, so the effect might be to drop
massive
On 2008-05-02, David Woolley <[EMAIL PROTECTED]> wrote:
> I'm not very familiar with orphan mode, but I think even orphan mode
> uses an average of the time from the adjacent nodes, and doesn't
> identify a single correct node. Even if it does, it will only select
> from its immediate neighbou
Steve Kostecke wrote:
> Orphan mode provides a means for a group of systems to automomously
> elect a leader in the event that no real time sources are reachable. The
> leader is selected based on a random value which is generated by each
> ntpd at start-up.
That's different from timed (Berkeley
Kevin Oberman wrote:
>> Date: Fri, 2 May 2008 07:37:32 -0500
>> From: "Ryan Malayter" <[EMAIL PROTECTED]>
>> Sender: [EMAIL PROTECTED]
>>
>>
>> On Thu, May 1, 2008 at 12:25 PM, Steve Kostecke <[EMAIL PROTECTED]> wrote:
>>
>>> You should always append iburst to your server lines.
>> Aussuming that w
Unruh wrote:
> "David L. Mills" <[EMAIL PROTECTED]> writes:
>
>> Brian,
>
>> The longest delay NTP response was from the Moon, as simulated at JPL.
>> Next step is the Mars orbiters and then the rovers. JPL discovered the
>> max distance threshold had to be increased to handle the Moon delay.
>
[EMAIL PROTECTED] (Danny Mayer) writes:
>Unruh wrote:
>> "David L. Mills" <[EMAIL PROTECTED]> writes:
>>
>>> Brian,
>>
>>> The longest delay NTP response was from the Moon, as simulated at JPL.
>>> Next step is the Mars orbiters and then the rovers. JPL discovered the
>>> max distance threshol
Unruh wrote:
> [EMAIL PROTECTED] (Danny Mayer) writes:
>
>> Unruh wrote:
>>> "David L. Mills" <[EMAIL PROTECTED]> writes:
>>>
Brian,
The longest delay NTP response was from the Moon, as simulated at JPL.
Next step is the Mars orbiters and then the rovers. JPL discovered the
m
12 matches
Mail list logo
