Roger Oberholtzer wrote:
I have had issues on openSUSE with ntp and servers that are only available after a user runs NetworkManager. On a laptop out in the world using wireless, NetworkManager rather than the traditional ifup method is a fact of life. I always have to run 'rcntp restart' after I get a connection. Otherwise, even after a couple hours, ntp does not cotton on to the availability of the server - even though it is still running. Simply restarting ntp corrects that.
I sense a NetworkManager problem rather than an ntp ditto. Have you ever checked ntp's status after such a network change? I mean, check the status of the time sources.
If ntp was setting the time correct without needing the external server,
How can it? It has to rely on the stored RTC values, possibly using known drift to correct them.
I would expect a reasonable time when the system restarts. In my case, the BIOS is two hours off (UTC time, and I am in Stockholm). Until I run 'rcntp restart' AFTER the network connection is made, the time will remain incorrect by two hours.
I suspect a timezone issue, not an NTP problem.
ntp seems to deal with the timezone when the server is available. Does it not deal with it when the server is not available? Hard to say. But it looks that way. It really looks to me that ntp does nothing to the time if an external time source is not found.
Check your logs - you should see ntp sync'ing to the local clock. Unless that is not configured? -- Per Jessen, Zürich (21.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org