Per Jessen wrote:
Joachim Schrod wrote:
It is also clear that the switching of time servers according to availability and quality works very well, just as it is (fairly) clear that Roger's problem is more of a timezone issue than an ntp ditto.
I wasn't referring to Roger's laptop problem. That clearly seems like a configuration error. I referred to his goal to get robust and reliable time syncs in his automotive IT systems, i.e., in embedded car systems with intermittent GPS connections.
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. But polling is not good for Roger's automotive IT use case and should be avoided anyhow, we have already agreed upon that.) Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org