[58791] in North American Network Operators' Group
Re: NTp sources that work in a datacenter (was Re: Is latency
daemon@ATHENA.MIT.EDU (Peter Lothberg)
Sun Jun 1 02:06:51 2003
Date: Sat, 31 May 2003 23:05:09 PDT
From: Peter Lothberg <roll@stupi.se>
To: "Steven M. Bellovin" <smb@research.att.com>
Cc: Joel Jaeggli <joelja@darkwing.uoregon.edu>,
Steve Francis <steve@expertcity.com>, Michael.Dillon@radianz.com,
nanog@merit.edu
In-Reply-To: Your message of Wed, 14 May 2003 12:38:43 -0400
Errors-To: owner-nanog-outgoing@merit.edu
>
> In message <Pine.LNX.4.44.0305140802170.7544-100000@twin.uoregon.edu>, Joel Jae
> ggli writes:
> >
> >
> >Also if you just need a high level of syncronization between the time on
> >all your hosts you can just deploy one standalone ntp server, sync it
> >against public time sources and get everything synced against that. its
> >probably a 95% solution to most people's timeing needs.
> >
>
> If I recall correctly, NTP assumes that latency = RTT/2. You might
> make it work well for his application *if* you set up your tree so that
> your paths are each one hop, or at least symmetric over your network.
Correct, and if it's asymetric you get a static offset. My laptops
internal clock is a bigger source of error...
-P
