[SuSE Linux] Re: Can't keep time
Brad Shelton <bshelton@ole.ole.net> responds:
After you set the time, you need to write it to the hardware clock. Othwise it'll continue to get the wrong time from the hardware clock.
To set the hardware clock, as root do clock -w.
Thanks, Brad, and others. I guess it goes to show how long it's been since I've upgraded; my ancient Slackware setup wrote to the hardware clock whenever I did a simple `date.' I'd never heard of the `clock' or `hwclock' commands. Another question occurs, though. In my previous setup, changes to/from Daylight Savings Time were automatic. I assume knowledge of these changes is in the Linux software, not the hardware clock, but in any case, I never had to perform any administrative tasks at that time of year. In fact, I could check with Linux if I was in doubt if this was the time of changeover. Since I bought this machine just before last fall's change from DST, and I rarely reboot, I suspect SuSE 5.3 does NOT update the hardware clock after the DST change, but the normal Linux date routines know when the change occurs and adjust the soft clock, and that's why I didn't know anything was amiss. What do you all recommend now to cope with DST? Should a routine be added somewhere to write to the hardware clock when a change to/from DST occurs, say, as a twice-a-year cron task? If so, does anyone have a favorite cron spec for USA DST? I'm suspicious that my hardware clock is likely not very accurate, given that it seemed to be off noticably in the short time I halted my machine in my testing. What do you folks recommend as a source of accurate time? Is your computer crystal clock pretty good? Do you periodically dial up a standards bureau? Favorite suggestions? Given all the capabilities of clock(8) and hwclock it's tempting to go for some accuracy. My current /etc/adjtime is all zeros. Thanks again, Jim - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
On Sun, Jan 31, 1999 at 12:39:37PM -0800, Jim Osborn wrote:
Thanks, Brad, and others. I guess it goes to show how long it's been since I've upgraded; my ancient Slackware setup wrote to the hardware clock whenever I did a simple `date.' I'd never heard of the `clock' or `hwclock' commands.
Hmmm. It was using slackware that I discovered this, originally.
Another question occurs, though. In my previous setup, changes to/from Daylight Savings Time were automatic. I assume knowledge of these changes is in the Linux software, not the hardware clock, but in any case, I never had to perform any administrative tasks at that time of year. In fact, I could check with Linux if I was in doubt if this was the time of changeover.
This setup (SuSE 5.4) handles it just fine if you have the time zone information set properly. I just put a 0300 cron job to write the hardware clock every day.
Since I bought this machine just before last fall's change from DST, and I rarely reboot, I suspect SuSE 5.3 does NOT update the hardware clock after the DST change, but the normal Linux date routines know when the change occurs and adjust the soft clock, and that's why I didn't know anything was amiss.
More'n likely.
What do you all recommend now to cope with DST? Should a routine be added somewhere to write to the hardware clock when a change to/from DST occurs, say, as a twice-a-year cron task? If so, does anyone have a favorite cron spec for USA DST?
I'm suspicious that my hardware clock is likely not very accurate, given that it seemed to be off noticably in the short time I halted my machine in my testing. What do you folks recommend as a source of accurate time? Is your computer crystal clock pretty good? Do you periodically dial up a standards bureau? Favorite suggestions? Given all the capabilities of clock(8) and hwclock it's tempting to go for some accuracy. My current /etc/adjtime is all zeros.
I use xntpd to keep all the clocks on my networks sync-ed and, as I said above, I set the hardware clocks at 0300 every day. That way, no matter what anomaly I run into with the clocks, including a hardware clock that isn't very accurate, I set it once per day based on the network time protocol and that seems to do quite nicely. -------------------------------------------- Brad Shelton bshelton@ole.net On Line Exchange <A HREF="http://ole.net"><A HREF="http://ole.net</A">http://ole.net</A</A>> Detroit News <A HREF="http://detnews.com"><A HREF="http://detnews.com</A">http://detnews.com</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (2)
-
bshelton＠ole.ole.net -
jimo＠eskimo.com