In article ,
David Woolley writes:
>Miguel Gon=E7alves wrote:
>> What is a typical offset of the loop without using special oscillators?
>> Is less than 1 us achievable?
>Depends on the network or reference clock, and the resolution to which
>the local clock can be read.
It also depends upon t
On Mon, Sep 26, 2011 at 23:58, wrote:
> The documention states that MD5keys will be lss then or equal to 16
> characters in length, and consist of a printable ASCII characters and
> be terminated by whitespace or #. Yet the output of 'ntp-keygen -M',
> and the examples shown in the documentation
On 2011-09-26, Miguel Gon?alves wrote:
> Hi Richard!
>
> On 26 September 2011 22:39, Richard B. Gilbert wrote:
>>
>> What is a typical offset of the loop without using special oscillators? Is
>>> less than 1 us achievable?
>>>
>>
>> I don't believe that accuracy of 1 microsecond , or less, is obt
2011/9/26 Miguel Gonçalves :
> 2011/9/26 Dave Hart
>> 2011/9/25 Miguel Gonçalves :
>> > I have a machine running FreeBSD 7.4 and it seems that the CPU clock
>> > runs
>> > too fast or slow (positive offset in loopstats is fast or slow?).
>>
>> ntpd's offset and the frequency compensation are both
All,
I have a very dumb question, regarding what information is correct,
and what is not.
The documention states that MD5keys will be lss then or equal to 16
characters in length, and consist of a printable ASCII characters and
be terminated by whitespace or #. Yet the output of 'ntp-keygen -M',
an
Just a small correction...
2011/9/27 Miguel Gonçalves
>
> Your chances of obtaining 1 microsecond accuracy using clocks on the
>> internet is just about nil! OTOH very few people actually need
>> microsecond accuracy for anything other than "bragging rights"!
>>
>
> I know... :-) My cable connec
Hi Richard!
On 26 September 2011 22:39, Richard B. Gilbert wrote:
>
> What is a typical offset of the loop without using special oscillators? Is
>> less than 1 us achievable?
>>
>
> I don't believe that accuracy of 1 microsecond , or less, is obtainable
> without without installing a GPS Timing R
On 9/26/2011 9:41 AM, Miguel Gonçalves wrote:
2011/9/26 Dave Hart
2011/9/25 Dave Hart:
2011/9/25 Miguel Gonçalves:
tick# tail -10 /var/log/ntp/loopstats
55829 66927.314 0.11263 185.398 0.00620 0.001452 4
55829 66942.315 0.11355 185.398 0.00402 0.001358 4
55829 66957.315 0.000
Miguel Gonçalves wrote:
What is a typical offset of the loop without using special oscillators? Is
less than 1 us achievable?
Depends on the network or reference clock, and the resolution to which
the local clock can be read.
___
questions mailing
On 2011-09-26, Cristian Seceleanu wrote:
> I don't know how i managed to get blacklisted on support.ntp.org but
> this happened while attempting to submit my time servers to the
> stratum two list.
>
> I think i submited one of my servers without selecting proper stratum
> and then tried to edit
On 26 September 2011 02:07, Doug Calvert wrote:
> tickadj always tells me I am silly when I give it the -A described in
> the docs for optimized tick. I looked at tickadj.c quickly and did
> not see any facilities for -A
>
Hi Doug!
If you are running FreeBSD I suggest changing the mach.tsc_freq
2011/9/26 Dave Hart
> 2011/9/25 Dave Hart :
> > 2011/9/25 Miguel Gonçalves :
> >
> >> tick# tail -10 /var/log/ntp/loopstats
> >> 55829 66927.314 0.11263 185.398 0.00620 0.001452 4
> >> 55829 66942.315 0.11355 185.398 0.00402 0.001358 4
> >> 55829 66957.315 0.10197 185.398 0.00
Hi Dave!
2011/9/26 Dave Hart
> 2011/9/25 Miguel Gonçalves :
> > I have a machine running FreeBSD 7.4 and it seems that the CPU clock runs
> > too fast or slow (positive offset in loopstats is fast or slow?).
>
> ntpd's offset and the frequency compensation are both reported as
> corrections to t
[Sorry for such a long message]
Hi David!
On 25 September 2011 20:55, David Woolley wrote:
> Miguel Gonçalves wrote:
>
>>
>> I have a machine running FreeBSD 7.4 and it seems that the CPU clock runs
>> too fast or slow (positive offset in loopstats is fast or slow?).
>>
>
> Neither. A constant
14 matches
Mail list logo