On Fri, Mar 23, 2012 at 06:12:11PM +0100, Terje Mathisen wrote:
Miroslav Lichvar wrote:
On Fri, Mar 23, 2012 at 11:49:19AM +0100, Terje Mathisen wrote:
But I think a much bigger problem with the clock filter and PLL
combination is that it can't drop more than 7 samples. When the
network is
unruh wrote:
No I would not. That is not what ntpd does. It really does throw away 7
of the samples and never uses them. The whole question is what is the
best statistic to use. I do not believe that the shortest roundtrip
time is that best statistic. If you could convince me it is, I would be
On Fri, Mar 23, 2012 at 11:49:19AM +0100, Terje Mathisen wrote:
unruh wrote:
No I would not. That is not what ntpd does. It really does throw away 7
of the samples and never uses them. The whole question is what is the
best statistic to use. I do not believe that the shortest roundtrip
time
Miroslav Lichvar wrote:
On Fri, Mar 23, 2012 at 11:49:19AM +0100, Terje Mathisen wrote:
But I think a much bigger problem with the clock filter and PLL
combination is that it can't drop more than 7 samples. When the
network is saturated, it's usually better to drop much more than. If
the
On 2012-03-23, Terje Mathisen terje.mathisen at tmsw.no wrote:
unruh wrote:
No I would not. That is not what ntpd does. It really does throw away 7
of the samples and never uses them. The whole question is what is the
best statistic to use. I do not believe that the shortest roundtrip
time is
On 2012-03-22, Dennis Ferguson dennis.c.fergu...@gmail.com wrote:
On 21 Mar, 2012, at 11:36 , unruh wrote:
On 2012-03-21, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
I noticed that Dave Hart later posted this reply to your question. I'll
reference that below.
NTP's jitter
unruh un...@invalid.ca wrote in message
news:dG5ar.18461$pc1.11...@newsfe11.iad...
[]
No confusion. I understood completely. Ron had a machine on GPS which
ran away. You got a report of a 1 sec slippage. The question is whether
or not a 1 sec slippage in the GPS could trigger a runaway on a
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote in message
news:4f692255.2020...@c3energy.com...
On 3/20/2012 11:21 AM, David J Taylor wrote:
[]
You /will/ see variation in the serial output from the Sure device, as
you will in many NMEA devices. For the Sure device, one measurement
On Wed, Mar 21, 2012 at 06:49, David J Taylor wrote:
(Is jitter RMS, SD, peak-to-peak?).
NTP's jitter is root mean squares of offsets from the clock filter
register (last 8 responses, more or less).
Dave Hart
___
questions mailing list
On Wed, Mar 21, 2012 at 06:49, David J Taylor wrote:
(Is jitter RMS, SD, peak-to-peak?).
NTP's jitter is root mean squares of offsets from the clock filter
register (last 8 responses, more or less).
Dave Hart
Thanks, Dave. Makes good sense.
Cheers,
David
On 3/21/2012 2:49 AM, David J Taylor wrote:
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote in message
news:4f692255.2020...@c3energy.com...
On 3/20/2012 11:21 AM, David J Taylor wrote:
[]
You /will/ see variation in the serial output from the Sure device,
as you will in many NMEA
On 3/20/2012 8:27 PM, Rick Jones wrote:
Ron Frazier (NTP)timekeepingntpl...@c3energy.com wrote:
On 3/20/2012 5:48 PM, E-Mail Sent to this address will be added to the
BlackLists wrote:
unruh wrote:
Dave Harth...@ntp.org wrote:
frequency adjustments aren't
On 2012-03-21, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
On 3/21/2012 2:49 AM, David J Taylor wrote:
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote in message
news:4f692255.2020...@c3energy.com...
On 3/20/2012 11:21 AM, David J Taylor wrote:
[]
You /will/ see
NTP's jitter is root mean squares of offsets from the clock filter
register (last 8 responses, more or less).
unruh wrote:
Strange, because ntp then takes that entry of those 8
with the shortest roundtrip time and uses only it to
drive the ntp algorithm. Thus on the one hand it is using
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote in message
news:4f69e531.7070...@c3energy.com...
[]
C) What your ntp plotter plots as the red line on the jitter tab with a
loopstats file. Not sure how that's derived.
Red-line: jitter straight out of the loopstats data. Scale on
On 3/20/2012 2:59 PM, unruh wrote:
On 2012-03-20, David J Taylordavid-tay...@blueyonder.co.uk.invalid wrote:
unruhun...@invalid.ca wrote in message
news:d13ar.7952$gv1.7...@newsfe12.iad...
[]
It is really really hard to imagine any gps device doing that.
Yes, I agree, and yet what just
On 21 Mar, 2012, at 11:36 , unruh wrote:
On 2012-03-21, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
I noticed that Dave Hart later posted this reply to your question. I'll
reference that below.
NTP's jitter is root mean squares of offsets from the clock filter
register
unruh un...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in the world did the system go nuts
when it was on Local. That itself should not have happened.
If some software had told the system clock to run fast, it simply stays
On Tue, Mar 20, 2012 at 02:59:12AM +, Dave Hart wrote:
Although it's the first time I've seen such, it appears the offset and
frequency calculations both ended up overflowing. I would have
guessed bad input should have appeared in peerstats before loopstats
but I didn't find anything
On 3/20/2012 2:25 AM, David J Taylor wrote:
unruh un...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in the world did the system go nuts
when it was on Local. That itself should not have happened.
If some software had told the
On Tue, Mar 20, 2012 at 12:28, Miroslav Lichvar mlich...@redhat.com wrote:
On Tue, Mar 20, 2012 at 02:59:12AM +, Dave Hart wrote:
Although it's the first time I've seen such, it appears the offset and
frequency calculations both ended up overflowing. I would have
guessed bad input should
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote in message
[]
Hypothetically speaking, what if I don't want it to distribute time if
it's working in internet mode?
Run a Perl script one a minute, looking for the GPS line in ntpq -p
output, and if the tally code isn't * (or whatever,
[]
David Taylor is right that it is normal for Windows to keep running
the clock at whatever rate was last set after the program setting the
rate goes away. It's also true that Windows does not have any rate
limits itself -- you can easily tell Windows to advance the clock 1
usec per tick
On Tue, Mar 20, 2012 at 15:55, David J Taylor wrote:
How does NTPD_TICKADJ_PPM affect this? If that was set to -800, for
example, wouldn't the adjustment range be -300/-1300 rather than +/-500?
Yes, it would.
Cheers,
Dave Hart
___
questions mailing
Ron Frazier (NTP) wrote:
On 3/20/2012 2:25 AM, David J Taylor wrote:
unruh un...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in the world did the system go nuts
when it was on Local. That itself should not have happened.
If
On 2012-03-20, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote:
unruh un...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in the world did the system go nuts
when it was on Local. That itself should not have happened.
On 2012-03-20, Dave Hart h...@ntp.org wrote:
On Tue, Mar 20, 2012 at 12:28, Miroslav Lichvar mlich...@redhat.com wrote:
On Tue, Mar 20, 2012 at 02:59:12AM +, Dave Hart wrote:
Although it's the first time I've seen such, it appears the offset and
frequency calculations both ended up
On 2012-03-20, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
On 3/20/2012 2:25 AM, David J Taylor wrote:
unruh un...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in the world did the system go nuts
when it was on
unruh un...@invalid.ca wrote in message
news:d13ar.7952$gv1.7...@newsfe12.iad...
[]
It is really really hard to imagine any gps device doing that.
Yes, I agree, and yet what just popped up in my mail box but a reference
to:
an inexplicable 1 second slip of 3 GPS based NTP time sources.
I
On 3/20/2012 1:25 PM, unruh wrote:
On 2012-03-20, Ron Frazier (NTP)timekeepingntpl...@c3energy.com wrote:
On 3/20/2012 2:25 AM, David J Taylor wrote:
unruhun...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in
On Tue, Mar 20, 2012 at 17:28, unruh un...@invalid.ca wrote:
On 2012-03-20, Dave Hart h...@ntp.org wrote:
David Taylor is right that it is normal for Windows to keep running
the clock at whatever rate was last set after the program setting the
rate goes away. It's also true that Windows does
Hi David L,
See below.
On 3/20/2012 1:00 PM, David Lord wrote:
Ron Frazier (NTP) wrote:
On 3/20/2012 2:25 AM, David J Taylor wrote:
unruh un...@invalid.ca wrote in message
news:JDU9r.22132$_c5.11...@newsfe09.iad...
[]
Of course the question still is why in the world did the system go
nuts
On 2012-03-20, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote:
unruh un...@invalid.ca wrote in message
news:d13ar.7952$gv1.7...@newsfe12.iad...
[]
It is really really hard to imagine any gps device doing that.
Yes, I agree, and yet what just popped up in my mail box but a
unruh un...@invalid.ca wrote in message
news:Ur4ar.15722$iq1.15...@newsfe18.iad...
On 2012-03-20, David J Taylor david-tay...@blueyonder.co.uk.invalid
wrote:
unruh un...@invalid.ca wrote in message
news:d13ar.7952$gv1.7...@newsfe12.iad...
[]
It is really really hard to imagine any gps device
Ron,
I think the below is correct enough but accuracy is only one dimension of
NTP server performance.As you have found one other dimension is
reliability.
It does little good to have a system that is running at pico-second level
But jumps ahead two years at rare unpredictable times. (It
On 2012-03-20, David J Taylor david-tay...@blueyonder.co.uk.invalid wrote:
unruh un...@invalid.ca wrote in message
news:Ur4ar.15722$iq1.15...@newsfe18.iad...
On 2012-03-20, David J Taylor david-tay...@blueyonder.co.uk.invalid
wrote:
unruh un...@invalid.ca wrote in message
On 2012-03-20, Dave Hart h...@ntp.org wrote:
On Tue, Mar 20, 2012 at 17:28, unruh un...@invalid.ca wrote:
On 2012-03-20, Dave Hart h...@ntp.org wrote:
David Taylor is right that it is normal for Windows to keep running
the clock at whatever rate was last set after the program setting the
rate
Ron Frazier (NTP) wrote:
Hi David L,
See below.
On 3/20/2012 1:00 PM, David Lord wrote:
Ron Frazier (NTP) wrote:
Hi David T,
Eventually, I do plan to have the server preferences as follows:
Time server machine:
GPS
Internet as backup
Hypothetically speaking, what if I
unruh wrote:
Dave Hart h...@ntp.org wrote:
frequency adjustments aren't compounded like that.
Lets hope not, but on his system, something DID trigger a runaway.
What about power saving frequency management of the core
NTP is using?
--
E-Mail Sent to this address
On 2012-03-20, David Lord sn...@lordynet.org wrote:
Ron Frazier (NTP) wrote:
Hi David L,
See below.
On 3/20/2012 1:00 PM, David Lord wrote:
Ron Frazier (NTP) wrote:
Hi David T,
Eventually, I do plan to have the server preferences as follows:
Time server machine:
GPS
On 3/20/2012 5:19 PM, David Lord wrote:
Ron Frazier (NTP) wrote:
Hi David L,
See below.
On 3/20/2012 1:00 PM, David Lord wrote:
Ron Frazier (NTP) wrote:
Hi David T,
Eventually, I do plan to have the server preferences as follows:
Time server machine:
GPS
Internet as backup
On 3/20/2012 5:48 PM, E-Mail Sent to this address will be added to the
BlackLists wrote:
unruh wrote:
Dave Harth...@ntp.org wrote:
frequency adjustments aren't compounded like that.
Lets hope not, but on his system, something DID trigger a runaway.
What about power
On 3/20/2012 11:21 AM, David J Taylor wrote:
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote in message
[]
Hypothetically speaking, what if I don't want it to distribute time
if it's working in internet mode?
Run a Perl script one a minute, looking for the GPS line in ntpq -p
output,
Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
On 3/20/2012 5:48 PM, E-Mail Sent to this address will be added to the
BlackLists wrote:
unruh wrote:
Dave Harth...@ntp.org wrote:
frequency adjustments aren't compounded like that.
Lets hope not, but on
Rick Jones wrote:
Ron Frazier wrote:
BlackList wrote:
unruh wrote:
Dave Hart wrote:
frequency adjustments aren't compounded like that.
Lets hope not, but on his system, something DID trigger a runaway.
What about power saving frequency management of the core NTP is using?
I doubt that's
Ron,
I don't know what the heck happened either, but there are a few clues.
You didn't tell us which version of ntpd you're using or which OS
it's running on. Skimming the huge ntp.conf for non-comment lines I
see it appears to be some version of Windows.
Take note of the last line in the
Ron Frazier (NTP) wrote:
the clock said Aug 2014
the clock was advancing at a rate of about 2 HR per actual second.
appeared to be updating about twice per second rather than once
ever 10 seconds. It said that the preferred clock was LOCL
Remove LOCL.
I thought others had mentioned it might
Hi Dave H,
Thanks for the info and for looking into the issue. I meant that the
clock was psycho, not the PC. The PC is normally very tame and
cooperative, as cooperative as Windows gets anyway. These GPS
experiments have certainly brought several surprises though.
I run both Windows and
On Tue, Mar 20, 2012 at 03:56, Ron Frazier (NTP) wrote:
Hi Dave H,
Thanks for the info and for looking into the issue. I meant that the clock
was psycho, not the PC.
Right, I got that. You were ever so politely screaming for attention
regarding software I volunteer to help maintain. How
On 2012-03-20, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
Hi all,
I just came home from supper to the most NOT charming experience. I had
left with my PC clock syncing nicely to my Globalsat BU-353 GPS. When I
came home, I found the clock said Aug 2014 and visually could see
On 3/20/2012 12:11 AM, Dave Hart wrote:
On Tue, Mar 20, 2012 at 03:56, Ron Frazier (NTP) wrote:
Hi Dave H,
Thanks for the info and for looking into the issue. I meant that the clock
was psycho, not the PC.
Right, I got that. You were ever so politely screaming for attention
On 3/20/2012 12:09 AM, unruh wrote:
On 2012-03-20, Ron Frazier (NTP)timekeepingntpl...@c3energy.com wrote:
Hi all,
I just came home from supper to the most NOT charming experience. I had
left with my PC clock syncing nicely to my Globalsat BU-353 GPS. When I
came home, I found the clock
On 2012-03-20, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
On 3/20/2012 12:09 AM, unruh wrote:
On 2012-03-20, Ron Frazier (NTP)timekeepingntpl...@c3energy.com wrote:
Hi all,
I just came home from supper to the most NOT charming experience. I had
left with my PC clock
On 2012-03-20, Ron Frazier (NTP) timekeepingntpl...@c3energy.com wrote:
Hi Dave H,
Thanks for the info and for looking into the issue. I meant that the
clock was psycho, not the PC. The PC is normally very tame and
cooperative, as cooperative as Windows gets anyway. These GPS
54 matches
Mail list logo
