Roger Oberholtzer wrote:
On Mon, 2011-07-18 at 19:36 +0200, Per Jessen wrote:
Joachim Schrod wrote:
I had big problems in the past when ntpd decides that a time source is too unreliable and either drops it, or maybe even terminates itself because all time sources are too much off.
But localhost would surely always be available?
That's not the problem. If you start ntpd with only localhost, and if a time server gets available later whose time is different by more than 20 minutes, ntpd will terminate itself. (To be more precise: the difference must be as large for some polls, 8 IIRC, to get a full reach shift register of 0377.
I agree, this is a potential problem. (the sanity check is 1000s ~ 16min).
Can I be sure ntp knows that my 2 hour time difference on the hardware clock is correct and not an error? Remember that the hardware clock is UTC time. And we do not all live in that timezone.
ntp doesn't care about timezones. http://en.wikipedia.org/wiki/Network_Time_Protocol "It provides Coordinated Universal Time (UTC). No information about time zones or daylight saving time is transmitted; this information is outside its scope and must be obtained separately." -- Per Jessen, Zürich (16.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org