Per Jessen said the following on 07/15/2011 12:05 PM:
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.
+1
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?
Indeed. At startup, in the absence of an outside reference (or until an outside reference can be obtained -- however long that takes) there is the hardware clock, which may drift. NTP 'learns' the drift rate of the clock, and keeps 'learning'. So what information does chrony have that NTP doesn't? -- The emphasis should be on "why" we do a job - W. Edwards Deming -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org