Roger Oberholtzer wrote:
On Fri, 2011-07-15 at 18:05 +0200, Per Jessen wrote:
This massaging does seem to happen when ntp is running and after it has a server. But I am not convinced that anything is done when ntp starts and before it gets in contact with a server.
If properly configured ntp will _always_ have a server - the local clock. The drift of the local clock oscillator will have been determined, so ntp will use that to keep massaging the clock until a better source becomes available.
But the localclock, when ntp is used, is from the BIOS, which is UTC, which is incorrect.
I would not have thought that timezone is important here. What is your priority - correct time or an accurate clock? I expect the latter, so what is the significance of the time-of-day?
And that is what chrony provides. A useful estimate of time before the first server is found.
I don't know anything about chrony, so I have to wonder what information it has that ntp does not?
It is not so much that it has different information. In fact, in many ways it is like ntp. The difference is subtle. Whereas ntp does not seem to retry non-existent servers (real 'not localhost'), chrony does.
ntp does too. You saw the logfile I posted yesterday. If your ntp setup fails to switch between the configured time sources according to their quality&availability, something is wrong with your ntp setup. -- Per Jessen, Zürich (15.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org