Roger Oberholtzer said the following on 07/15/2011 07:16 PM:
Try running 'hwclock -r' to read it. I am on a laptop that exhibits the problem. hwclock -r is showing the correct UTC time that I expect. The network is up via NetworkManager when I logged in graphically. The ntp that started when I booted is still running. But, alas, the time is incorrect. It can sit like this for hours, and the time will NEVER be corrected. Ever. Consistently.
All I have to do now is run 'rcntp restart', and time will be corrected.
Hmm. That sounds to me as if the initial NTP failed and locked up. I might speculate that it came up before the network was up and went into a state that assumed an outside reference would NEVER be available. The restart killed that old one and brought up a new one that DID see the network etc etc etc. As someone said in this thread, its a boot sequence problem. Ah for 'systemd' -- Those who wish to seek out the cause of miracles, and to understand the things of nature as philosophers, and not to stare at them in astonishment like fools, are soon considered heretical and impious,and proclaimed as such by those whom the mob adores as the interpreters of nature and the gods. For these men know that once ignorance is put aside that wonderment would be taken away which is the only means by which their authority is preserved. --Spinoza -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org