On Mon, Feb 13, 2012 at 07:13, David J Taylor
wrote:
> "unruh" wrote in message
> news:AMVZq.14470$9j5@newsfe09.iad...
>
>> The problem on windows is I believe that there is no way to alter the
>> system clock rate.
I know there's a popular religious belief among some techies that
Windows is
Terje Mathisen wrote:
But doesn't the HAL clock also support _both_ a fixed/baseline clock
frequency adjustment, and a temporary adjustment to be applied over the
next N time slices/seconds?
Yes. My assumption of only one mechanism may be unsound.
___
On Sun, Feb 12, 2012 at 21:44, David Woolley
wrote:
> unruh wrote:
>
>> The problem on windows is I believe that there is no way to alter the
>> system clock rate. On linux, one can permanantly alter the rate at which
>
> Altering the software clock rate (time added to system time per tick) is the
On Mon, Feb 13, 2012 at 07:56, David Woolley
wrote:
> Terje Mathisen wrote:
>
>> But doesn't the HAL clock also support _both_ a fixed/baseline clock
>> frequency adjustment, and a temporary adjustment to be applied over the next
>> N time slices/seconds?
>
> Yes. My assumption of only one mechan
That's OCXO, oven controlled crystal oscillator. Why X for crystal?
Christ if I know. There's a great article at
http://en.wikipedia.org/wiki/Crystal_oscillator
that includes a table of abbreviations you can refer to.
Cheers,
Dave Hart
X is easier to write than "Crys" and it's shorter in Mo
On Mon, Feb 13, 2012 at 01:37, A C wrote:
> On 2/12/2012 16:38, David Lord wrote:
>>
>> A C wrote:
>>>
>>> I'm not exactly sure what happened but I may have caught the system in
>>> the act of trying to run away. Below is the last two lines from the
>>> peers log for one of the peers and below tha
"Dave Hart" wrote in message
news:CAMbSiYDUXf3g4qk_ng2xcgu70=RxMqyrFj-35qMmAU6-
[]
Sad fact: No matter how well ntpd is able to discipline the clock on
Windows, other apps are generally stuck with a low-precision system
clock. It may be sync'd to within less than 100 usec to UTC, but when
app
On Mon, Feb 13, 2012 at 08:50, David J Taylor
wrote:
> "Dave Hart" wrote in message
> news:CAMbSiYDUXf3g4qk_ng2xcgu70=RxMqyrFj-35qMmAU6-
>
>> Sad fact: No matter how well ntpd is able to discipline the clock on
>> Windows, other apps are generally stuck with a low-precision system
>> clock. It
A C wrote:
On 2/12/2012 16:38, David Lord wrote:
A C wrote:
I'm not exactly sure what happened but I may have caught the system in
the act of trying to run away. Below is the last two lines from the
peers log for one of the peers and below that is the output of ntpq
showing what happened to tha
On Sun, Feb 12, 2012 at 05:31, Mark C. Stephens wrote:
[next line is quoting David Taylor]
>> > Let's know what happens with the Rockwell Jupiter - I don't know that box.
>
> I fired it up, ah ntpd v4.2.7p253 doesn't seem to recognise refclock 31
> anymore
> which got a giggle out of me :)
>
> I
On Sun, Feb 12, 2012 at 07:08, Mark C. Stephens wrote:
> Ah I just tried palisade driver and I am getting
> Palisade(1) HW_poll: ioctl(fd, SET, RTS_on): Inappropriate I/O control
> operation
As with refclock_jupiter.c, refclock_palisade.c is compiled on Windows
ntpd 4.2.7p253 but to my knowledge
On Sun, Feb 12, 2012 at 19:04, Mark C. Stephens wrote:
> No PPS on Winnt but works okay on freebsd with exactly the same config:
That configuration uses flag3 1 to request via PPSAPI that the kernel
synchronize directly to the PPS. That's a no-go using serialpps.sys
PPSAPI on Windows, as Windows
On Sat, Feb 11, 2012 at 22:16, Chuck Swiger wrote:
> On Feb 11, 2012, at 11:58 AM, Dave Hart wrote:
>> On Sat, Feb 11, 2012 at 17:17, Chuck Swiger wrote:
Have you tried to time the minimum clock reading time with RDTSC
or GetPerformance* counter calls?
I wrote a tiny test prog
On Sat, Feb 11, 2012 at 19:02, unruh wrote:
> On 2012-02-11, Dave Hart wrote:
>> On Sat, Feb 11, 2012 at 01:03, unruh wrote:
>>> On 2012-02-09, bombjack wrote:
What happens if I change the time on the server, lets say 5 years
forward? Will the client sync to the server? and If so, how
On Sat, Feb 11, 2012 at 23:56, Ron Frazier (NTP)
wrote:
> Thanks for the note. I have prefer on my gps line in ntp.conf. I have to do
> more testing. I thought I saw it select another clock anyway some time
> during the day. I know the GPS was available at the time and it wasn't
> insane.
Check y
On Sun, Feb 12, 2012 at 16:32, Ron Frazier (NTP)
wrote:
> On 02/12/2012 02:43 AM, Mark C. Stephens wrote:
>>
>> Wow I just stopped ntpd and restarted, 1.3 seconds that time!
>>
>> I just bring it back with ntpdate...
>>
>> C:\Program Files\NTP\bin>ntpdate -b 192.168.5.112
>> 12 Feb 18:41:53 ntpdat
semi OT ( either OnTopic or OffTopic ;-):
What happens if I kill ntpd during clock slewing ?
What happens if I SIGTERM ntpd during clock slewing ?
uwe
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On 2/13/2012 2:36 AM, Dave Hart wrote:
On Sun, Feb 12, 2012 at 19:03, Chuck Swiger wrote:
On Feb 12, 2012, at 9:36 AM, unruh wrote:
The clock crystal ages, and suffers internal crystal "cracks"
migrations, etc, which change the frequency of the crystal. Thus even in
a temperature controlled ov
On Feb 12, 2012, at 11:36 PM, Dave Hart wrote:
>> Agreed, temperature swings will have a major impact on the crystal frequency.
>
> Well, I know what you're saying but we're talking on the order of 1
> PPM / degree C.
Yeah, on that order. It's noticeable, or can be anyway, but also well within
t
On Mon, Feb 13, 2012 at 10:59 AM, Chuck Swiger wrote:
>>> You might be able to improve the stability of the crystal by ensuring good
>>> airflow and cooling via HVAC as needed. And I suppose you could adjust the
>>> rate by changing the HVAC set-point, but I don't think the benefit is worth
>>>
On Feb 13, 2012, at 4:06 AM, Dave Hart wrote:
>> A clock is an oscillator and a counter. (Go read VMWare's
>> "Timekeeping-In-VirtualMachines.pdf" or PHK's
>> "timecounter.pdf" for considerably more detailed description
>> and examples if this is unclear.)
>
> By your definition, NTP was develope
On 2/13/2012 01:53, David Lord wrote:
A C wrote:
On 2/12/2012 16:38, David Lord wrote:
A C wrote:
I'm not exactly sure what happened but I may have caught the system in
the act of trying to run away. Below is the last two lines from the
peers log for one of the peers and below that is the outp
On 2/13/2012 00:49, Dave Hart wrote:
You can force the remote sources to poll less frequently using minpoll
on their server lines. I make no promises that is a wise thing to do,
though. I presume there's a good reason ntpd does not raise the
polling interval on peers when the system polling int
Uwe Klein wrote:
semi OT ( either OnTopic or OffTopic ;-):
What happens if I kill ntpd during clock slewing ?
What happens if I SIGTERM ntpd during clock slewing ?
I don't think you have fully constrained the problem. In some
environments the slew will stop, although I'm not sure whether i
Dave Hart wrote:
> Unruh and Terje are talking about a MTK (I or II?) chipset.
Likely the MediaTek GPS chips (mtk.com.tw);
Although there have been others that copied / cloned
/ started with their protocol, even though they are
different GPS chips, their "MTK" protocol is compatible,
except
A C wrote:
On 2/13/2012 01:53, David Lord wrote:
A C wrote:
On 2/12/2012 16:38, David Lord wrote:
A C wrote:
I'm not exactly sure what happened but I may have caught the system in
the act of trying to run away. Below is the last two lines from the
peers log for one of the peers and below that
On 2/13/2012 15:44, David Lord wrote:
Recent ntpd is supposed to handle that level of frequency
offset but most of my pcs have had the frequency offset
adjusted to be < 10 ppm which is done when I build a kernel
with "options PPS_SYNC" and "options TIMER_FREQ=119".
This kernel does have PP
On 2/13/2012 16:26, A C wrote:
On 2/13/2012 15:44, David Lord wrote:
Recent ntpd is supposed to handle that level of frequency
offset but most of my pcs have had the frequency offset
adjusted to be < 10 ppm which is done when I build a kernel
with "options PPS_SYNC" and "options TIMER_FREQ=119?
On 2012-02-13, Dave Hart wrote:
> On Sun, Feb 12, 2012 at 17:36, unruh wrote:
>> Uh, that is what ntp tries to do, and is why it shifts up its poll
>> interval as time goes along ( and since it throws away 80% of
>> measurments, the effective poll interval is about 8 times as long as the
>> actua
On 2012-02-13, Dave Hart wrote:
> On Sat, Feb 11, 2012 at 10:20, Terje Mathisen wrote:
>> unruh wrote:
>>> GEt the manual from Mediatex MTK NMEA Packet User Manual, which gives a
>>> far far more extensive set of nmea programming instructions for the
>>> chipset that Sure uses.
>>
>>
>> Does that
On 2/13/2012 3:25 PM, Chris Albertson wrote:
On Mon, Feb 13, 2012 at 10:59 AM, Chuck Swiger wrote:
You might be able to improve the stability of the crystal by ensuring good
airflow and cooling via HVAC as needed. And I suppose you could adjust the
rate by changing the HVAC set-point, but
On 2/13/2012 3:25 PM, Chris Albertson wrote:
On Mon, Feb 13, 2012 at 10:59 AM, Chuck Swiger wrote:
You might be able to improve the stability of the crystal by ensuring good
airflow and cooling via HVAC as needed. And I suppose you could adjust the
rate by changing the HVAC set-point, but I
"A C" wrote in message
news:4f398579.9060...@acarver.net...
[]
I'm not sure it's a good idea either but I would really like to
understand why a refclock clamps the polling interval at such a low
value when nearly every bit of documentation says we should be kind to
NTP servers and make sure t
33 matches
Mail list logo
