On 26/04/2013 20:20, David Woolley wrote:
David Taylor wrote:
I don't see that here. With a local PPS reference you get within a
few microseconds within an hour. If the precision needed is less than
that,
We are discussing getting a good frequency lock, so that it will coast
well, rather
David Taylor wrote:
On 26/04/2013 20:20, David Woolley wrote:
David Taylor wrote:
I don't see that here. With a local PPS reference you get within a
few microseconds within an hour. If the precision needed is less than
that,
We are discussing getting a good frequency lock, so that it
unruh writes:
On 2013-04-26, Harlan Stenn st...@ntp.org wrote:
unruh writes:
Define occasionally. Unfortuneately ntpd requires about 5-10 hours to
rediscipline a clock to ultimate accuracy when the connection comes up
again, so if the connection time is shorter than that, chrony (assuming
Is there a way to configure ntpd so that when the offset exceeds 1
millisecond polling will automatically be set to 64 seconds or less?
If I understand correctly, polling currently is adjusted by the speed of
change in offset. It takes forever for a large offset to be skewed at
large polling
I think Harlan may have a valid point here.
For some, better may mean My clock frequency is stable and I am
tracking the middle of the clique as opposed to I am tighty latched
to the server I am currently listening to.
H
___
questions mailing
Mischanko, Edward T wrote:
Is there a way to configure ntpd so that when the offset exceeds 1
millisecond polling will automatically be set to 64 seconds or less?
That wouldn't generally be desirable, as, of many, the reason for this
would be a temporary change in network asymmetry, which is
Mischanko, Edward T wrote:
Is there a way to configure ntpd so that when the offset exceeds 1
millisecond polling will automatically be set to 64 seconds or less?
Although you can't do this, if you do have a situation where the time
measurements never have an error more than x, but there is
On 27/04/2013 09:13, David Woolley wrote:
[]
If the time error is low and bounded the frequency error does not
necessarily have a low error bound. Simply polling fast and using a
short loop time constant can give you a low error bound on the time, if
the network delays are stable and the source
On 2013-04-27, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 27/04/2013 09:13, David Woolley wrote:
[]
If the time error is low and bounded the frequency error does not
necessarily have a low error bound. Simply polling fast and using a
short loop time constant can give you a
On 2013-04-27, Mischanko, Edward T edward.mischa...@arcelormittal.com wrote:
Is there a way to configure ntpd so that when the offset exceeds 1
millisecond polling will automatically be set to 64 seconds or less?
If I understand correctly, polling currently is adjusted by the speed of
On 2013-04-27, Harlan Stenn st...@ntp.org wrote:
unruh writes:
On 2013-04-26, Harlan Stenn st...@ntp.org wrote:
unruh writes:
Define occasionally. Unfortuneately ntpd requires about 5-10 hours to
rediscipline a clock to ultimate accuracy when the connection comes up
again, so if the
Hello All ,
On Sat, 27 Apr 2013, Mischanko, Edward T wrote:
I think Harlan may have a valid point here.
For some, better may mean My clock frequency is stable and I am
tracking the middle of the clique as opposed to I am tighty latched
to the server I am currently listening to.
H
On 27/04/2013 17:37, unruh wrote:
[]
Try altering the ntpd drift file (eg representing say 2 days of outage,
not 10 seconds or what used to happen is that Linux's boot recalibration
of the clock would jump by 10s of PPM on each reboot).
Subract 20 from that value and then start it again.
[]
In article T8Tet.8216$zh4.3...@newsfe13.iad, unruh un...@invalid.ca
wrote:
On 2013-04-27, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 27/04/2013 09:13, David Woolley wrote:
[]
If the time error is low and bounded the frequency error does not
necessarily have a low error
On 2013-04-27, Joe Gwinn joegw...@comcast.net wrote:
In article T8Tet.8216$zh4.3...@newsfe13.iad, unruh un...@invalid.ca
wrote:
On 2013-04-27, David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
On 27/04/2013 09:13, David Woolley wrote:
[]
If the time error is low and bounded the
15 matches
Mail list logo
