>>> In article <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>> writes:
michael> VxWorks 5.4 and Radstone PPC1A
We haven't had anybody actively maintaining the VxWorks code in a while.
I do not know what versions of VxWorks were supposed to be working with NTP
and which ones wer
[EMAIL PROTECTED] (Moe Trin) writes:
>The Apple Rendezvous (renamed 'Bonjour' as a result of trademark
Thanks for the scuttlebutt about Rendezvous.
> Why are you allowing your users to screw with system configuration
> files?
Not anytime I call the shots. I'm a strong advocate of using r
On Tue, 22 May 2007, in the Usenet newsgroup comp.protocols.time.ntp, in
article <[EMAIL PROTECTED]>, Wolfgang S. Rupprecht wrote:
>I just watched a Google Talk series video about Bonjour, their
>zero-configuration hack.
The Apple Rendezvous (renamed 'Bonjour' as a result of trademark
violation),
On 2007-05-23, Wolfgang S. Rupprecht wrote:
> Steve Kostecke <[EMAIL PROTECTED]> writes:
>
> Looking at the usage graphs of the pools, there are only 2-6 million
> pools users. That probably accounts for most of the ntp users in the
> world. The current estimates are over 400 million internet-co
Dave wrote:
> I'm experiencing large values of dispersion when I use 'ntpq -p':
>
> 3:22pm:ntp>ntpq -p
> remote refid st t when poll reach delay
> offsetdisp
> ==
> *10.2.100.10 .GPS.
On May 18, 10:39 pm, Harlan Stenn <[EMAIL PROTECTED]> wrote:
> >>> In article <[EMAIL PROTECTED]>, Harlan Stenn <[EMAIL PROTECTED]> writes:
>
> Harlan> Michael, What is the old legacy system of which you speak?
>
> I mean OS/hardware.
>
> H
VxWorks 5.4 and Radstone PPC1A
_
Steve Kostecke <[EMAIL PROTECTED]> writes:
> 1. Multicast associations can not compensate for changing network
> conditions at each poll.
I'm picturing a second class of home user or small business that would
be very happy to have their computers all within a second of the
correct time and within
I'm experiencing large values of dispersion when I use 'ntpq -p':
3:22pm:ntp>ntpq -p
remote refid st t when poll reach delay
offsetdisp
==
*10.2.100.10 .GPS.1 u 25 64 377
Wolfgang S. Rupprecht wrote:
> Some mode that uses multicast for the timekeeping itself seems to me
> would be the lowest impact way to serve the millions of home systems.
> It just seems too tantalizing to pass up.
There are a few things to consider about Multicast:
1. Multicast associations ca
I had a couple of extranenous lines in the previous version of these
files:
# Minimal ntp.conf for Manycasting Client (on 224.0.1.1)
driftfile /var/lib/ntp/ntp.drift
keys/etc/ntp.keys
trustedkey 1
manycastclient 224.0.1.1 key 1
# Minimal ntp.conf for Manycasting Server (on 224.0.1.1)
d
Steve Kostecke <[EMAIL PROTECTED]> writes:
> Multicast and Manycast modes are completely different; I believe that
> you may be confusing the two.
Yea, I had assumed both modes used multicast for the timekeeping.
Thanks for the explanation.
Some mode that uses multicast for the timekeeping itsel
11 matches
Mail list logo
