Greg Freemyer wrote:
What NTP does do that you have ommited in this thread is also significant. It keeps track of drift of the system clock. In fact when a reference is available it keeps track of the drift continuously, so that when it starts up and isn't in contact with a reference it can make a damn good estimate of what the time really is.
I believe that is the theory, but I setup a dedicated laptop to act as a weather station a couple years ago. openSUSE based.
And I can say openSUSE on bootup does NOT behave that way. I suspect ntpd is way too slow to kick off and get things straightened out.
I have not updated the distro since it is a dedicated purpose machine and the is nothing of value on it, so I'd guess it is 10.3 or 11 based.
I can say with certainty that openSUSE on that laptop gets the time horribly wrong on reboot. (ie. its off by months.)
RTC battery bad? (surely they still have a battery?)
In my case, NTP uses the Internet sites for time but it seems to be invoked before the network is up, so it takes quite a while to fix the machines time. And when it does that, it must not be updating the bios clock, or it wouldn't be so horribly far off.
/var/log/ntp ought to tell you what's going on. -- Per Jessen, Zürich (20.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org