Re: [ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread David Woolley
David J Taylor wrote: > > Would it be any better for the routine to lie, and just give to the > nearest MHz, rounded down? That would result in an excessive error for those not using time synchronisation software, and would produce extreme instability if the frequency was very close to the ex

Re: [ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread David J Taylor
Hal Murray wrote: >>> Linux seme to be having a real real problem with its time >>> calibration routines. It's drift rate jumps on reboot by up to >>> 50PPM from one reboot to the next. > >> Really? I don't recall ever seeing that. > > I thought it was well known. It's been discussed here several/

Re: [ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread Hal Murray
>> Linux seme to be having a real real problem with its time calibration >> routines. It's drift rate jumps on reboot by up to 50PPM from one >> reboot to the next. >Really? I don't recall ever seeing that. I thought it was well known. It's been discussed here several/many times. I've seen jump

Re: [ntp:questions] Group Buy: GPS Receiver LGSF 3000-Buying Group

2009-01-18 Thread Unruh
hal-use...@ip-64-139-1-69.sjc.megapath.net (Hal Murray) writes: >>Sounds like it is pretty useless for timing (unless you happy with 10s of >>msec) No PPS, bluetooth delivery of information with all its latencies and >>variability. Why are you advertising it in a time group? >I assumed it was s

Re: [ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread Unruh
Steve Kostecke writes: >On 2009-01-18, Unruh wrote: >> Rob van der Putten writes: >> >>>One of my Debian Lenny boxes more then halved it's 'frequency' after a >>>software update (among others, kernel and ntpd). It used to be 43 ppm >>>and is now below 17 ppm and still dropping. Is this normal?

Re: [ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread Steve Kostecke
On 2009-01-18, Unruh wrote: > Rob van der Putten writes: > >>One of my Debian Lenny boxes more then halved it's 'frequency' after a >>software update (among others, kernel and ntpd). It used to be 43 ppm >>and is now below 17 ppm and still dropping. Is this normal? I've seen a different frequen

[ntp:questions] Group Buy: GPS Receiver LGSF2000 -Wholesale Price, Flexible Quantity

2009-01-18 Thread google-...@ready-market.com
GPS Receiver LGSF2000 is Taiwan made GPS Receiver, OEM, ODM GPS receiver, Ready-Market Group Buying Service guaranteed factory prices and flexible quantity. Bluetooth GPS receiver LGSF2000 - compact design with internal passive antenna, bluetooth wireless technology and build in flash based firmwar

Re: [ntp:questions] Group Buy: GPS Receiver LGSF 3000-Buying Group

2009-01-18 Thread Hal Murray
>Sounds like it is pretty useless for timing (unless you happy with 10s of >msec) No PPS, bluetooth delivery of information with all its latencies and >variability. Why are you advertising it in a time group? I assumed it was spam. The spammer noticed that GPS had been mentioned in this group s

Re: [ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread Unruh
Rob van der Putten writes: >Hi there >One of my Debian Lenny boxes more then halved it's 'frequency' after a >software update (among others, kernel and ntpd). It used to be 43 ppm >and is now below 17 ppm and still dropping. >Is this normal? Linux seme to be having a real real problem with i

[ntp:questions] Sudden drop in frequency after software update

2009-01-18 Thread Rob van der Putten
Hi there One of my Debian Lenny boxes more then halved it's 'frequency' after a software update (among others, kernel and ntpd). It used to be 43 ppm and is now below 17 ppm and still dropping. Is this normal? Regards, Rob ___ questions mailing lis

Re: [ntp:questions] Peer vs. Server lines in NTP.CONF

2009-01-18 Thread David Woolley
Brown, Ken F. wrote: > > The NTP.CONF file for the 3 time servers (with GPS devices) have lines > similar to below (different com ports involved): > > server 127.127.1.0 #allow synchronization with local > clock > fudge 127.127.1.0 stratum 12 refid LOCAL Delete these two lines