[EMAIL PROTECTED] wrote: > > The title of my message was "Tip for more precise ntpd ?" which means it > is intended to provide a tip for pool servers admin that may find it > useful. I gave up long ago on requesting ntpd changes. Ntpd is simply not > designed for modern networks with asymmetrical delays. I would be more in > favor of a complete re-write but this is another story. > > You can still use ntpd for pool services requiring +-100 ms but as > demonstrated, it is easy to do better than the current ntpd > implementation quite easily. > Are you sure your network is modern when it has so huge delays that you are getting problems with ntpd? On the ADSL network here at home and at work, a roundtrip delay to a system at the provider is in the 5-6 ms range. Sure it will be asymmetrical (I have no method to measure that) but the total delay (and thus the potentitial asymmetry) is so small that this is nothing to worry about.
You could have big trouble when using a satellite-based access (especially with some other means of uplink), but fortunately that is not common. What kind of delays do you see on your networks, and are these really modern networks with a decent capacity planning? Or are you not talking about modern networks, but about saturated networks that the provider never modernizes? Even when ntpd has some accuracy problems, it seems a bit strange to consider openntpd as an alternative. Openntpd has accuracy at its lowest of all priority, or at least this is stated on the project page. Rob _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
