> > In message <[EMAIL PROTECTED]>, 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
