Dave Hart wrote:
> Are you using ntpd on Windows and dissatisfied with its timekeeping?
> I have a patched ntpd with changes intended to improve its accuracy
> that could use some wider testing. Source and binaries are linked to
> below.
>
> Two changes are particularly noteworthy:
>
> 1. Code
Richard B. Gilbert wrote:
> j...@sailorfej.net wrote:
>> Hi folks,
>>
>> I have a some FreeBSD systems running as guests in Microsoft Virtual
>> Server. There is a known problem with these were the clocks run very
>> fast. I am trying to use ntpd to keep their clocks in sync, but the
>> frequency
Take 2:
On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
wrote:
>
> I've installed your version, and included -M in my startup parameters:
>
> I get Event Log (Application) messages about stuff like:
>
> System time quantum 1.000 msec, min. slew 6.410 ppm/s
Notice the observed qu
On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
wrote:
>
> I've installed your version, and included -M in my startup parameters:
>
> I get Event Log (Application) messages about stuff like:
>
> System time quantum 1.000 msec, min. slew 6.410 ppm/s
> Clock interrupt period 15.600
Dave Hart wrote:
> Take 2:
>
> On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
> wrote:
>> I've installed your version, and included -M in my startup parameters:
>>
>> I get Event Log (Application) messages about stuff like:
>>
>> System time quantum 1.000 msec, min. slew 6.410 p
Danny Mayer wrote:
> Dave Hart wrote:
>> Take 2:
>>
>> On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
>> wrote:
>>> I've installed your version, and included -M in my startup parameters:
>>>
>>> I get Event Log (Application) messages about stuff like:
>>>
>>> System time quantum
On Jan 29, 4:52 am, ma...@ntp.isc.org (Danny Mayer) wrote:
> Dave Hart wrote:
> > Take 2:
>
> > On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
> > wrote:
> >> I've installed your version, and included -M in my startup parameters:
>
> >> I get Event Log (Application) messages abou
Dave Hart wrote:
> On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
> wrote:
>> I've installed your version, and included -M in my startup parameters:
>>
>> I get Event Log (Application) messages about stuff like:
>>
>> System time quantum 1.000 msec, min. slew 6.410 ppm/s
>> Clock
Just my $.02, and y'all know Im not a windows guy.
Yes, it would be ideal to have the timekeeping be as good as possible under
all circumstances.
And along the way we will continue to find situations that just mess us up,
and other places where we learn that doing better under X causes us to do
w
ma...@ntp.isc.org (Danny Mayer) writes:
>Dave Hart wrote:
>> Take 2:
>>
>> On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
>> wrote:
>>> I've installed your version, and included -M in my startup parameters:
>>>
>>> I get Event Log (Application) messages about stuff like:
>>>
>>
Dave Hart wrote:
> On Jan 29, 4:52 am, ma...@ntp.isc.org (Danny Mayer) wrote:
>> Dave Hart wrote:
>>> Take 2:
>>> On Jan 28, 11:52 pm, Terje Mathisen <"terje.mathisen at tmsw.no">
>>> wrote:
I've installed your version, and included -M in my startup parameters:
I get Event Log (Applicatio
On Jan 29, 11:38 am, Harlan Stenn wrote:
>
> If we can automatically detect when a "behavior shift" is needed and effect
> that change, great.
>
> If we cannot automatically detect these situations but we have a mechanism
> that would allow folks to select the behavior that is best for them, that'
I have now managed, with the patient help from Bill U., to get my Linux NTP
system running using the PPS signal from a Garmin 18x LVC. I thought I
would share what I had to do to make it all work.
* References:
http://time.qnan.org/
http://time.qnan.org/shmpps.tar
http://www.david-taylor.myb
On Jan 29, 12:54 pm, ma...@ntp.isc.org (Danny Mayer) wrote:
> Dave Hart wrote:
> > Most likely, Windows
> > Server 2008 has exactly the same behavior as Vista. It's entirely
> > reasonable on a server to know that you won't run Flash, Quicktime, or
> > Java.
>
> Actually that's untrue. We run Tomc
On Thu, 29 Jan 2009, phil.new...@wendysarbys.com wrote:
> - If you have NMEA output from the GPS in your ntp.conf file
> (127.127.20.0), expect it to have "reach 0" reported when you finally get
> PPS (127.127.28.0) working. You can have NMEA or PPS from your serial
> input, you just can't have b
> > PPS (127.127.28.0) working. You can have NMEA or PPS from your serial
> > input, you just can't have both at the same time from the same GPS on the
> > same port.
>
> There is no reason why you could not have both, except that the programs (eg
> shmpps) has not been written to use both. It is
Folkert van Heusden wrote:
> I use the pps patch by rodolpho giometti together with udo van den
> heuvel's patch to ntpd. Now my ntp syncs to both the nmea and the pps
> part of my garmin:
> remote refid st t when poll reach delay offset jitter
> ===
Dave Hart wrote:
> On Jan 29, 11:38 am, Harlan Stenn wrote:
>> If we can automatically detect when a "behavior shift" is needed and effect
>> that change, great.
>>
>> If we cannot automatically detect these situations but we have a mechanism
>> that would allow folks to select the behavior that i
18 matches
Mail list logo
