Roger Oberholtzer said the following on 07/15/2011 09:55 AM:
Systems that are on all the time or for very long periods of time do not see the deficiency in ntp. It has become apparent in systems that are off and on with some frequency. It is a recurring topic on the gpsd mailing list.
You seem to have ommitted a number of things. Many of us live on laptops that are "off and on with some frequency" and don't always have internet connections or in circumstances where the proxy doesn't allow NTP. What NTP does do that you have ommited in this thread is also significant. It keeps track of drift of the system clock. In fact when a reference is available it keeps track of the drift continuously, so that when it starts up and isn't in contact with a reference it can make a damn good estimate of what the time really is. The issue is "how good", and that can only be determined in any instance by experimentation. The other point is the _QUALITY_ of your internal clock. I _KNOW_ my wall clocks drift, about a minute month. I expect better of my TAG Heuer Aquagraph. I you (or your company) is unwilling to invest in the quality of baseline hardware to meet your business needs then arguing about NTP vs chrony is moot. -- Farming looks mighty easy when your plow is a pencil, and you're a thousand miles from the corn field. Dwight D. Eisenhower, September 11, 1956 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org