Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Terje Mathisen <"terje.mathisen at tmsw.no"> wrote: > unruh wrote: > > And it sounds like you have assymetric delays. Note that most ISPs > > deliver very different rates for up vs down, and that may well > > come with assymetric delays. (eg 600Kb/s, vs 30Mb/s for my cable > > access) > Ouch! >

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

> >>> 64 bytes from 87.186.242.38: icmp_seq=1 ttl=254 time=48.3 ms > >> 64 bytes from 87.186.242.38: icmp_seq=1 ttl=245 time=34.7 ms > > Reply from 87.186.242.38: bytes=32 time=43ms TTL=239 I like the different TTL values, showing how many hops there are between .38 and the folks pinging it. Ba

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/18/2012 04:03, David J Taylor wrote: I prefer fiber: 50/50 Mbit, very consistent ping times of a couple of ms to most no.pool.ntp.org servers. :-) Cost is about $75/month. Terje Maybe I should move to Norway! You are lucky! I pay US $48 (equivalent) for my 30/1 service! Don't complain

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

David J Taylor wrote: "Rob" wrote in message news:slrnjmbdn3.9ce.nom...@xs8.xs4all.nl... Uwe Klein wrote: Regular DSL here has quite large and spread line delays though speed is much higher delay is similar or slightly larger than forex ISDN. PING 87.186.242.38 (87.186.242.38) 56(84) bytes

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Rob" wrote in message news:slrnjmbdn3.9ce.nom...@xs8.xs4all.nl... Uwe Klein wrote: Regular DSL here has quite large and spread line delays though speed is much higher delay is similar or slightly larger than forex ISDN. PING 87.186.242.38 (87.186.242.38) 56(84) bytes of data. ( my first ping

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Ron Frazier (NTP)" wrote in message news:4f65006d.4090...@c3energy.com... [] Come to think of it, my comment about the polling interval not increasing may only apply to a local refclock, not a local server. You may be right - all the servers on this test system are Internet servers. Can

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

I prefer fiber: 50/50 Mbit, very consistent ping times of a couple of ms to most no.pool.ntp.org servers. :-) Cost is about $75/month. Terje Maybe I should move to Norway! You are lucky! I pay US $48 (equivalent) for my 30/1 service! Cheers, David

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Uwe Klein wrote: > Regular DSL here has quite large and spread line delays > though speed is much higher delay is similar or slightly larger than > forex ISDN. > PING 87.186.242.38 (87.186.242.38) 56(84) bytes of data. ( my first pingable > outside node ) > 64 bytes from 87.186.242.38: icmp_seq=1

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

David J Taylor wrote: "John Hasler" wrote in message news:87sjh7mlqs@thumper.dhh.gt.org... David J Taylor writes: But in the UK from Virgin Media I have 30 Mb/s down, 1 Mb/s up. I have been promised an upload speed increase about 18 months ago to 2 Mb/s up, which is more sensible...

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Ron Frazier (NTP) wrote: On 3/17/2012 6:00 PM, Terje Mathisen wrote: I prefer fiber: 50/50 Mbit, very consistent ping times of a couple of ms to most no.pool.ntp.org servers. :-) Cost is about $75/month. Terje You're a lucky dude if that's even an option. For most purposes other than timing

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/17/2012 6:00 PM, Terje Mathisen wrote: David J Taylor wrote: "Terje Mathisen" <"terje.mathisen at tmsw.no"> wrote in message news:is9e39-6ve2@ntp6.tmsw.no... [] You should never accept much more than 10:1 speed difference between down and up. Terje "Should" - I agree. But in the UK

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

David J Taylor wrote: "Terje Mathisen" <"terje.mathisen at tmsw.no"> wrote in message news:is9e39-6ve2@ntp6.tmsw.no... [] You should never accept much more than 10:1 speed difference between down and up. Terje "Should" - I agree. But in the UK from Virgin Media I have 30 Mb/s down, 1 Mb/s

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/17/2012 3:20 PM, David J Taylor wrote: "Ron Frazier (NTP)" wrote in message news:4f64d793.9010...@c3energy.com... [] Hi David, I'm not sure what will happen if you simultaneously prefer and noselect the local server. Assuming the local stratum 1 server is the most stable time source,

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Ron Frazier (NTP)" wrote in message news:4f64d793.9010...@c3energy.com... [] Hi David, I'm not sure what will happen if you simultaneously prefer and noselect the local server. Assuming the local stratum 1 server is the most stable time source, you'll get a much better picture of what the

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/17/2012 11:48 AM, David J Taylor wrote: You'd get less jitter with DSL. -- John Hasler John, You have piqued my interest. I have just set up a Windows-8 PC with an ntp configuration not dissimilar to Ron's, in that it's using purely Internet servers but trying to monitor a local stratu

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

ch 16, 2012 7:56 PM > To: questions@lists.ntp.org > Subject: Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock > error. > > On 2012-03-16, Charles Elliott wrote: > > On the subject of accuracy, has anyone ever really looked at NTPD's > > offset filtering mechan

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

You'd get less jitter with DSL. -- John Hasler John, You have piqued my interest. I have just set up a Windows-8 PC with an ntp configuration not dissimilar to Ron's, in that it's using purely Internet servers but trying to monitor a local stratum-1 server as well. In essence: ___

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"John Hasler" wrote in message news:87sjh7mlqs@thumper.dhh.gt.org... David J Taylor writes: But in the UK from Virgin Media I have 30 Mb/s down, 1 Mb/s up. I have been promised an upload speed increase about 18 months ago to 2 Mb/s up, which is more sensible... Such a very high cable dow

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

David J Taylor writes: > But in the UK from Virgin Media I have 30 Mb/s down, 1 Mb/s up. I > have been promised an upload speed increase about 18 months ago to 2 > Mb/s up, which is more sensible... Such a very high cable download speed is a peak burst speeds on a shared medium. Your sustained p

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Terje Mathisen" <"terje.mathisen at tmsw.no"> wrote in message news:is9e39-6ve2@ntp6.tmsw.no... [] You should never accept much more than 10:1 speed difference between down and up. Terje "Should" - I agree. But in the UK from Virgin Media I have 30 Mb/s down, 1 Mb/s up. I have been p

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

unruh wrote: Would it be worth it to recruit an electrical or systems engineer who claimed to know something about filtering data to take a serious look at NTPD's data filtering approach? There has to be some reason that there is a David Mills claims to know about filtering data. Not that I al

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

ntp.org [mailto:questions-bounces+elliott.ch=verizon@lists.ntp.org] On Behalf Of Chris Albertson Sent: Thursday, March 15, 2012 5:22 PM To: unruh Cc: questions@lists.ntp.org Subject: Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error. On Thu, Mar 15, 2012 at 2:09 PM, unruh wrote:

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

.@lists.ntp.org [mailto:questions-bounces+elliott.ch=verizon@lists.ntp.org] On Behalf Of Chris Albertson Sent: Thursday, March 15, 2012 5:22 PM To: unruh Cc: questions@lists.ntp.org Subject: Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error. On Thu, Mar 15, 2012 at 2:09 PM, unruh w

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

...@lists.ntp.org] On Behalf Of Chris Albertson Sent: Thursday, March 15, 2012 5:22 PM To: unruh Cc: questions@lists.ntp.org Subject: Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error. On Thu, Mar 15, 2012 at 2:09 PM, unruh wrote: Unfortunately it is not that simple. T

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

lliott.ch=verizon....@lists.ntp.org] On >> Behalf Of Chris Albertson >> Sent: Thursday, March 15, 2012 5:22 PM >> To: unruh >> Cc: questions@lists.ntp.org >> Subject: Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock >> error. >> >> On Thu, Mar 15

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

; Behalf Of Chris Albertson > Sent: Thursday, March 15, 2012 5:22 PM > To: unruh > Cc: questions@lists.ntp.org > Subject: Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock > error. > > On Thu, Mar 15, 2012 at 2:09 PM, unruh wrote: > > > Unfortunate

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/15/2012 5:06 PM, unruh wrote: On 2012-03-15, Ron Frazier (NTP) wrote: On 2012-03-15, Ron Frazier (NTP) wrote: On 3/15/2012 11:42 AM, unruh wrote: On 2012-03-14, Ron Frazier (NTP)wrote: On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote:

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Mar 15, 2012, at 2:06 PM, unruh wrote: > Before hitting on 13 different servers, it would be better tofigure out > what the problem is that is giving you such lousy results. It's not hard to make an educated guess as to the cause; since the topology is: "PC Wifi --> Wifi router --> wired route

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Thu, Mar 15, 2012 at 2:09 PM, unruh wrote: > Unfortunately it is not that simple. That rate changes by significan > amounts. Thus the rate you get after a week may be very different than > the rate you get after an hour. That, I submit, is the chief obstacle to > having an accurate clock. And

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-15, Ron Frazier (NTP) wrote: >> >> On 2012-03-15, Ron Frazier (NTP) wrote: >> >>> On 3/15/2012 11:42 AM, unruh wrote: >>> On 2012-03-14, Ron Frazier (NTP) wrote: > On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote: > > >> On 3/14

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-15, Chris Albertson wrote: >> Basically you have a trade-off between frequency error and time offset. >> IIRC, polling quickly will reduce the offset, but you get greater frequency >> variations. > > > There is nothing magic about NTP. You have the exact same trade off > if you try an

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

> Basically you have a trade-off between frequency error and time offset. > IIRC, polling quickly will reduce the offset, but you get greater frequency > variations. There is nothing magic about NTP. You have the exact same trade off if you try and sync your wrist watch to the big town clock on

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-15, Ron Frazier (NTP) wrote: On 3/15/2012 11:42 AM, unruh wrote: On 2012-03-14, Ron Frazier (NTP) wrote: On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote: On 3/14/2012 4:00 PM, David J Taylor wrote: Hi David T, NOW you understand.

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-15, Ron Frazier (NTP) wrote: > On 3/15/2012 11:42 AM, unruh wrote: >> On 2012-03-14, Ron Frazier (NTP) wrote: >> >>> On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote: >>> On 3/14/2012 4:00 PM, David J Taylor wrote: >> Hi David T, >> >> NOW you

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/15/2012 11:42 AM, unruh wrote: On 2012-03-14, Ron Frazier (NTP) wrote: On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote: On 3/14/2012 4:00 PM, David J Taylor wrote: Hi David T, NOW you understand. PS to my prior message. I don't think the problem s

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Thu, Mar 15, 2012 at 12:47, Ron Frazier (NTP) wrote: > Speaking of which, is there a way to run ntpd and have it NOT > adjust the clock at all, but still generate stats files, so I can monitor > the clock frequency just based on the computer usage and nothing else? You might try "disable ntp"

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-14, Ron Frazier (NTP) wrote: > On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote: >> On 3/14/2012 4:00 PM, David J Taylor wrote: Hi David T, NOW you understand. I have 4 PC's connected to the LAN, plus my wife's work computer 3 days / week, and on rare oc

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Ron Frazier (NTP)" wrote in message news:4f61e4df.4080...@c3energy.com... [] I mainly meant that operating conditions will vary the frequency of the oscillator. Speaking of which, is there a way to run ntpd and have it NOT adjust the clock at all, but still generate stats files, so I can mo

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 6:42 PM, E-Mail Sent to this address will be added to the BlackLists wrote: Ron Frazier (NTP) wrote: My typical performance from internet servers is offsets of + / - 60 ms. # Why not try some that have a closer network distance, or are at least geographically closer? # G

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi Rick, Interesting thought. It's Windows 7. I don't know what it's time source is in technical terms, but it's a standard installation. I've got pretty much all the power management stuff turned off. The computer is set to never stand by or shut down when it's plugged into an AC outlet.

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/15/2012 4:34 AM, David J Taylor wrote: "Ron Frazier (NTP)" wrote in message news:4f61168b.8030...@c3energy.com... [] PS to my prior message. I don't think the problem so much is the delay to the internet servers, or even to get out of my house. NTPD is supposed to take care of that

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Ron Frazier (NTP)" wrote in message news:4f61168b.8030...@c3energy.com... [] PS to my prior message. I don't think the problem so much is the delay to the internet servers, or even to get out of my house. NTPD is supposed to take care of that as long as it's pretty much symmetrical. I t

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi David, I really appreciate all these suggestions you shared, as well as past ones. Based somewhat on been there, done that! If I decide to revamp my network, I'll probably put some of them into use. However, that's not really practical right now. All the networking gear is in the basem

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

unruh wrote: On 2012-03-14, David J Taylor wrote: "unruh" wrote in message news:I1T7r.36416$l12.35...@newsfe23.iad... [] Did you shut down and restart your computer? Did you perchance do this during the daylight savings time transition on a Windows system? Could the error be related to the fa

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Any chance these PCs are using a timesource (in the system somewhere) that isn't constant in the face of power management events? The other pink tiger (vs elephant) in your house could/would be the wifi - at least in terms of being a "stable" network type. Some of the bufferbloat

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Ron Frazier (NTP) wrote: > My typical performance from internet servers is offsets of + / - 60 ms. # Why not try some that have a closer network distance, or are at least geographically closer? # Georgia / Comcast Hints: tos cohort 1 restrict source nomodify pool us.pool.ntp.org iburst

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 5:04 PM, Ron Frazier (NTP) wrote: On 3/14/2012 4:00 PM, David J Taylor wrote: Hi David T, NOW you understand. I have 4 PC's connected to the LAN, plus my wife's work computer 3 days / week, and on rare occasions my son's computer. All are connected by wifi. All do pretty

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 4:00 PM, David J Taylor wrote: Hi David T, NOW you understand. I have 4 PC's connected to the LAN, plus my wife's work computer 3 days / week, and on rare occasions my son's computer. All are connected by wifi. All do pretty mundane things: web browser, email, sometimes d

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi David T, NOW you understand. I have 4 PC's connected to the LAN, plus my wife's work computer 3 days / week, and on rare occasions my son's computer. All are connected by wifi. All do pretty mundane things: web browser, email, sometimes downloading patches, sometimes doing online ba

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 12:35 PM, David J Taylor wrote: "Ron Frazier (NTP)" wrote in message news:4f60bc0c.8040...@c3energy.com... [] OK. Here are the loopstats from another computer for 7 days (in the chart). I don't have any peerstats for it. It has the same server list. One is preferred. All ser

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"unruh" wrote in message news:HI48r.39505$zd5.1...@newsfe12.iad... On 2012-03-14, David J Taylor <> wrote: [] Windows uses UTC internally, not local time. Local time is simply a presentation layer issue. Windows is unaffected by a DST transition. That must be new, since windows certainly u

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 11:31 AM, David Lord wrote: Ron Frazier (NTP) wrote: On 3/14/2012 7:14 AM, David Lord wrote: Ron Frazier (NTP) wrote: Based on advice from David Taylor, I just changed my configuration. Previously, I had only the GPS selectable and the internet servers noselected for te

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-14, Ron Frazier (NTP) wrote: > On 3/14/2012 3:03 AM, unruh wrote: >> On 2012-03-13, Ron Frazier (NTP) wrote: >> >>> Hi all, >>> >>> I just woke up to a 50 SECOND clock error. Prior to the error, with my >>> PC locked into the GPS and the internet servers noselected, here's what >>

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-14, David J Taylor wrote: > "unruh" wrote in message > news:I1T7r.36416$l12.35...@newsfe23.iad... > [] >> Did you shut down and restart your computer? Did you perchance do this >> during the daylight savings time transition on a Windows system? Could >> the error be related to the fac

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Ron Frazier (NTP)" wrote in message news:4f60bc0c.8040...@c3energy.com... [] OK. Here are the loopstats from another computer for 7 days (in the chart). I don't have any peerstats for it. It has the same server list. One is preferred. All servers are active. Performance is no better.

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Ron Frazier (NTP) wrote: On 3/14/2012 7:14 AM, David Lord wrote: Ron Frazier (NTP) wrote: Based on advice from David Taylor, I just changed my configuration. Previously, I had only the GPS selectable and the internet servers noselected for testing purposes to try to determine where a

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 10:41 AM, David J Taylor wrote: Hi David, OK. You asked for it. 8-) Well, I actually suggested /all/ the Internet servers being enabled, allowing NTP to make its best choice. When I'm through testing, I'll open up the other internet servers as a backup in case the GPS fails.

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi David, OK. You asked for it. 8-) Well, I actually suggested /all/ the Internet servers being enabled, allowing NTP to make its best choice. When I'm through testing, I'll open up the other internet servers as a backup in case the GPS fails. For now, I'm just running with one clock so

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 7:14 AM, David Lord wrote: Ron Frazier (NTP) wrote: On 3/13/2012 5:39 PM, David Lord wrote: Ron Frazier (NTP) wrote: On 3/13/2012 2:40 PM, Chris Albertson wrote: On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prio

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 3:03 AM, unruh wrote: On 2012-03-13, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats looked like. Baseline is the GPS. Colored lines

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/14/2012 2:46 AM, David J Taylor wrote: Hi David, OK, you've convinced me. I've put noselect on the GPS and taken it away on the New York NIST server. The NY NIST server is now preferred and polling from 1 - 4 minutes. Hopefully they won't ban me for hitting it too often. I think the

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Ron Frazier (NTP) wrote: On 3/13/2012 5:39 PM, David Lord wrote: Ron Frazier (NTP) wrote: On 3/13/2012 2:40 PM, Chris Albertson wrote: On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into t

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-13, Ron Frazier (NTP) wrote: > Hi all, > > I just woke up to a 50 SECOND clock error. Prior to the error, with my > PC locked into the GPS and the internet servers noselected, here's what > my peerstats looked like. Baseline is the GPS. Colored lines are > internet servers. > > ht

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"unruh" wrote in message news:I1T7r.36416$l12.35...@newsfe23.iad... [] Did you shut down and restart your computer? Did you perchance do this during the daylight savings time transition on a Windows system? Could the error be related to the fact that Windows like time on localtime not UTC? Wi

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi David, OK, you've convinced me. I've put noselect on the GPS and taken it away on the New York NIST server. The NY NIST server is now preferred and polling from 1 - 4 minutes. Hopefully they won't ban me for hitting it too often. I think the NIST server will have more jitter, particular

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 10:28 PM, Ron Frazier (NTP) wrote: On 3/13/2012 10:05 PM, unruh wrote: On 2012-03-13, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats look

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 10:05 PM, unruh wrote: On 2012-03-13, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats looked like. Baseline is the GPS. Colored lines

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 2012-03-13, Ron Frazier (NTP) wrote: > Hi all, > > I just woke up to a 50 SECOND clock error. Prior to the error, with my > PC locked into the GPS and the internet servers noselected, here's what > my peerstats looked like. Baseline is the GPS. Colored lines are > internet servers. Did y

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Mar 13, 2012, at 5:05 PM, Ron Frazier (NTP) wrote: > I don't have PPS on this computer. It has no serial port. When I get my > Sure board, assuming I can solder it without killing it, I'm going to try > bringing the PPS signal through a Prolific chipset based serial - USB > converter which

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 7:24 PM, Chuck Swiger wrote: On Mar 13, 2012, at 4:08 PM, Ron Frazier (NTP) wrote: I was speculating that perhaps my only selectable clock, the GPS, failed, and that something went nuts, and that's why I found the clock 50 seconds off this morning. However, I don't have any e

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Mar 13, 2012, at 4:08 PM, Ron Frazier (NTP) wrote: > I was speculating that perhaps my only selectable clock, the GPS, failed, and > that something went nuts, and that's why I found the clock 50 seconds off > this morning. However, I don't have any evidence of a GPS failure. In any > case,

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 6:42 PM, Chuck Swiger wrote: On Mar 13, 2012, at 3:19 PM, Ron Frazier (NTP) wrote: At that time, I had the GPS as the only selectable clock, for testing. I'm monitoring the internet servers for comparison. I've since selected 1 NIST server as the preferred and only selectabl

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Mar 13, 2012, at 3:19 PM, Ron Frazier (NTP) wrote: > At that time, I had the GPS as the only selectable clock, for testing. I'm > monitoring the internet servers for comparison. I've since selected 1 NIST > server as the preferred and only selectable clock, and am monitoring the GPS > and o

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 5:39 PM, David Lord wrote: Ron Frazier (NTP) wrote: On 3/13/2012 2:40 PM, Chris Albertson wrote: On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet se

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 5:01 PM, E-Mail Sent to this address will be added to the BlackLists wrote: Ron Frazier (NTP) wrote: I put the following in ntp.conf to allow the clock to coast in local mode if the GPS goes insane. # Allow system to coast on local clock if GPS is insane server 127.127.1.1 minpo

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Ron Frazier (NTP) wrote: On 3/13/2012 2:40 PM, Chris Albertson wrote: On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peer

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 4:27 PM, David J Taylor wrote: "Ron Frazier (NTP)" wrote in message news:4f5f9233.1080...@c3energy.com... [] The question is, what reset my clock abruptly 50 seconds off at around 0637 UTC. I would suspect your GPS. My loopstats file shows that the GPS was humming along quite

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Ron Frazier (NTP) wrote: > I put the following in ntp.conf to allow the clock to coast in local > mode if the GPS goes insane. > # Allow system to coast on local clock if GPS is insane > server 127.127.1.1 minpoll 3 maxpoll 6 # LCL, local clock > fudge 127.127.1.1 stratum 12 # increase

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

"Ron Frazier (NTP)" wrote in message news:4f5f9233.1080...@c3energy.com... [] The question is, what reset my clock abruptly 50 seconds off at around 0637 UTC. I would suspect your GPS. My loopstats file shows that the GPS was humming along quite nicely at that point with no anomalies at a

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 2:55 PM, Ron Frazier (NTP) wrote: On 3/13/2012 2:40 PM, Chris Albertson wrote: On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected,

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 2:40 PM, Chris Albertson wrote: On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats looked like. Baselin

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On Tue, Mar 13, 2012 at 9:52 AM, Ron Frazier (NTP) wrote: > Hi all, > > I just woke up to a 50 SECOND clock error.  Prior to the error, with my PC > locked into the GPS and the internet servers noselected, here's what my > peerstats looked like.  Baseline is the GPS.  Colored lines are internet >

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

On 3/13/2012 2:04 PM, David J Taylor wrote: Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats looked like. Baseline is the GPS. Colored lines are internet servers. [] My sys

Re: [ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats looked like. Baseline is the GPS. Colored lines are internet servers. [] My system is Windows 7, NTP 4.2.7p259, GPS GlobalSa

[ntp:questions] ARRGH!!! I woke up to a 50 SECOND clock error.

Hi all, I just woke up to a 50 SECOND clock error. Prior to the error, with my PC locked into the GPS and the internet servers noselected, here's what my peerstats looked like. Baseline is the GPS. Colored lines are internet servers. http://dl.dropbox.com/u/9879631/drifting01-peerstats.20