On Aug 7, 11:22 am, Steve Kostecke koste...@ntp.org wrote:
On 2010-08-07, Cindy Huyser chuy...@io.com wrote:
[---=| Quote block shrinked by t-prot: 32 lines snipped |=---]
My configuration file is very simple:
driftfile C:\Windows\Temp\ntp.drift
broadcastdelay 0.008
This has
I've added a bug to the database (bug 1600) for the problem with
resolving the IPv6 link local address prefix in Windows XP. Thanks
again for your help, everyone.
Best regards,
Cindy Huyser
___
questions mailing list
questions@lists.ntp.org
Wow, that is an old piece of equipment. I may be able to find
something. One of my first jobs at Datum was to add the SNMP and NTP
HMAC options to the TS2000. It is an old PC based design using Ampro
modules. If I can't find the manual, do you have a specific ??.
-Original Message-
No, this was the replacement to the TS2000. Completely different
cpu/os/codebase. And it came out in 1996 which just goes to show how
old that TS2000 is.
-Original Message-
From: questions-bounces+gdowd=symmetricom@lists.ntp.org
On Aug 7, 9:37 pm, Danny Mayer ma...@ntp.org wrote:
On 8/5/2010 5:53 PM, mval wrote:
Upgrading ntp from 4.2.0 to 4.2.6p1.
System receives time via broadcast over the wildcard interface.
That should not be happening. ntpd should be creating it's own receiving
interface for broadcast
Danny Mayer wrote:
Terje Mathisen wrote:
I have preached the same for a few years, but then I read an article
from/about VMware where one of their architects stated that the latest
ESX product gave even better results when running ntpd on the client OS.
Do you have a reference?
Although
BlackLists wrote:
Danny Mayer wrote:
Terje Mathisen wrote:
I have preached the same for a few years, but then I read an article
from/about VMware where one of their architects stated that the latest
ESX product gave even better results when running ntpd on the client OS.
Do you have a
