Richard B. Gilbert wrote:
Also note that Windows' clock "ticks" every 17 milliseconds.
Only when not running ntpd. ntpd forces the use of multimedia timers.
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
Alexander Petrov (Moscow, Russia) wrote:
In local network I can synchronize computers in range +-200 µs, and in
internet = +- 400 µs if use NTP servers pool.
It is no use synchronising to this accuracy if ordinary application
programs cannot read the time to the same precision.
___
Alexander Petrov (Moscow, Russia) wrote:
do { t2 = localTime ) while ( t1 == t2 );
This step is likely to be unacceptable for anyone who is actually trying
to create application time stamps to a high degree of accuracy.
Windows ntpd already does RDTSC calibration, although it cannot be
aff
On 21 окт, 00:59, E-Mail Sent to this address will be added to the
BlackLists wrote:
> > By default, the timer resolution 15.625 ms (1/64 second),
> > ... increase the timer resolution.
>
> Current PCs' HPET timer is in the few NanoSeconds range?
> and the ACPI timer is in the few dozen NanoSeco
On 21 окт, 00:59, E-Mail Sent to this address will be added to the
BlackLists wrote:
> > By default, the timer resolution 15.625 ms (1/64 second),
> > ... increase the timer resolution.
>
> Current PCs' HPET timer is in the few NanoSeconds range?
> and the ACPI timer is in the few dozen NanoSeco
In article ,
"David J Taylor" wrote:
> > I have a small network of Windows XP (64 bit) running simulations, with
> > NTPv4 running on all the boxes and using a GPS-based timeserver on the
> > company network. The ping time to the server is 2 milliseconds from my
> > desk, but I'm seeing random
> By default, the timer resolution 15.625 ms (1/64 second),
> ... increase the timer resolution.
Current PCs' HPET timer is in the few NanoSeconds range?
and the ACPI timer is in the few dozen NanoSeconds range?
--
E-Mail Sent to this address
will be added to the BlackLists.
__
> By default, the timer resolution 15.625 ms (1/64 second),
> ... increase the timer resolution.
Current PCs' HPET timer is in the few NanoSeconds range?
and the ACPI timer is in the few dozen NanoSeconds range?
--
E-Mail Sent to this address
will be added to the BlackLists.
__
Joseph Gwinn wrote:
I have a small network of Windows XP (64 bit) running simulations, with
NTPv4 running on all the boxes and using a GPS-based timeserver on the
company network. The ping time to the server is 2 milliseconds from my
desk, but I'm seeing random time errors of order plus/minus
On 2010-10-20, Miernik, Jerzy (Jerzy) wrote:
> Each ntp.conf contains a line 'tos orphan 10'.
> Each node had GPS but lost it. Local clocks (LCL) not configured.
Orphan Mode replaces the Undisciplined Local Clock driver (aka "LOCAL"
or "LCL").
> 'ntpg -np' in 10.103.86.6 shows this:
>
> remote
On 10/20/2010 12:44 PM, Alexander Petrov (Moscow, Russia) wrote:
On 20 окт, 16:54, Joseph Gwinn wrote:
I have a small network of Windows XP (64 bit) running simulations, with
NTPv4 running on all the boxes and using a GPS-based timeserver on the
company network. The ping time to the server is
Steve, thanks.
I have a two-node network
10.103.86.6 - 10.49.88.6
Each ntp.conf contains a line 'tos orphan 10'.
Each node had GPS but lost it. Local clocks (LCL) not configured.
'ntpg -np' in 10.103.86.6 shows this:
remote refidst
--
On 2010-10-20, Miernik, Jerzy (Jerzy) wrote:
> Is there a way to know that ntpds are working in orphan mode?
ntpd advertises a ref-id of 127.0.0.1 when it has switched to orphan
mode.
You'll have to have access to the configuration file to see if an
arbitrary ntpd is configured to use orphan mo
Miroslav Lichvar wrote:
> However, in my experience the NMEA sources tend to be quite bad. If
> you are not planning to run without PPS or would rather use an NTP
> source as a backup, remove the 127.127.28.0 line and use gpsd just for
> the PPS source.
That is very true! I have seen NMEA source
On Wed, Oct 20, 2010 at 12:54 UTC, Joseph Gwinn wrote:
> I have a small network of Windows XP (64 bit) running simulations, with
> NTPv4 running on all the boxes and using a GPS-based timeserver on the
> company network.
[...]
> The question is if this level of error is reasonable, given the setup
uwe writes:
> Oh, I forgot, you are in the US ;-)
The USA has had motorail since 1983. Bill, however, is in Canada.
--
John Hasler
jhas...@newsguy.com
Dancing Horse Hill
Elmwood, WI USA
___
questions mailing list
questions@lists.ntp.org
http://lists.
On 20 окт, 16:54, Joseph Gwinn wrote:
> I have a small network of Windows XP (64 bit) running simulations, with
> NTPv4 running on all the boxes and using a GPS-based timeserver on the
> company network. The ping time to the server is 2 milliseconds from my
> desk, but I'm seeing random time erro
unruh wrote:
That is I am afraid a terrible routing model. You will never get good
timing from it. GPS or no GPS. "I want to drive from New Yourk to San
Francisco as quicly as possible, but my car has one wheel locked by a
police boot, and the somebody put water into my gas tank. How can I get
fr
Dear experts,
Is there a way to know that ntpds are working in orphan mode?
Is there a way to identify which one is orphan parent?
Thanks,
Jerzy.
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On 2010-10-19, Miernik, Jerzy (Jerzy) wrote:
> Unruh and Terje, thank you for replying.
>
> What if we complicated networking somewhat, such that at times node50
> acquires GPS capability while node1 may looses it? Actually, to make the
> problem general, any one node (possibly only one) may ha
On Wed, Oct 20, 2010 at 07:00:50AM -0700, M Z wrote:
> I have another question. The fudge in ntp.conf for the GPS is suggested to be
> set at .420 - how can
> I calculate the best value? gpsd gives all kinds of debug information but
> what
> numbers tell me how delayed the GPS signal is compared
- Original Message
Sent: Mon, October 18, 2010 7:00:01 AM
Subject: questions Digest, Vol 72, Issue 16
Date: Sun, 17 Oct 2010 17:52:39 +0200
From: Miroslav Lichvar
On Sat, Oct 16, 2010 at 08:24:02AM -0700, M Z wrote:
I have both usglobalsat MR350P and garmin 18xLVC connected to ser
I have a small network of Windows XP (64 bit) running simulations, with
NTPv4 running on all the boxes and using a GPS-based timeserver on the
company network. The ping time to the server is 2 milliseconds from my
desk, but I'm seeing random time errors of order plus/minus 5 to 10
milliseconds, b
I have a small network of Windows XP (64 bit) running simulations, with
NTPv4 running on all the boxes and using a GPS-based timeserver on the
company network. The ping time to the server is 2 milliseconds from my
desk, but I'm seeing random time errors of order plus/minus 5 to 10
milliseconds
On 20 окт, 15:07, "Alexander Petrov (Moscow, Russia)"
wrote:
>http://192.168.10.245/forum/download/file.php?id=36
Sorry, local link :) Global is
http://forum.fora-capital.ru/forum/download/file.php?id=36
___
questions mailing list
questions@lists.ntp.o
New version released ( http://192.168.10.245/forum/download/file.php?id=36
)
+ improved logs and virtual clock stability.
+ english names for icons.
Notice, change setting NTPServers to nearest for you location, in file
conf/TMService.conf, sample:
NTPServers=0.us.pool.ntp.org;1.us.pool.ntp.org
_
Hello All!
I'm develop experimental tool TMService (
http://forum.fora-capital.ru/forum/download/file.php?id=35
), for precised time synchronization in local networks. This tool
allows you to synchronize time with online sources, and the virtual
clock (which is automatically calibrated) based on
27 matches
Mail list logo
