This article is from a FAQ concerning SCO operating
systems. While some of the information may be applicable to any OS,
or any Unix or Linux OS, it may be specific to SCO Xenix, Open
Desktop or Openserver.
There is lots of Linux, Mac OS X and general Unix info elsewhere on
this site: Search this site is the best
way to find anything.
Because it needs to be running at the time that "setclk" is run by crontab (3:01 AM by default). So if you are in the habit of not leaving your machine running at night, the change will not be made.
John Dubois explains: Because the time reported by the CMOS (motherboard) clock is *local time*, and local time includes the effects of DST. It has to, because the BIOS interprets it this way; if the OS tried to leave the CMOS clock set to non-DST time, the BIOS would report the wrong time and admins would "fix" it when they noticed the wrong time being reported.
So, if the system is booted and sees that it's July and 15:10, then it's July and 15:10. If it's booted and sees that the time is November and 15:12, it's November and 15:12. There is no attempt to shift time from what the CMOS clock reports. The CMOS clock is kept in sync with local time by adjusting it back or forward as neccessary when the DST transitions occur, via that /etc/setclk command in crontab. But this obviously only occurs if the system is running at the right time.
Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 3 | 29 | 50 | 50 | 5,247 |
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Click here to add your comments