IT pros battle clock and code in time change

TalkBack 21 of 40:

Next »

« Previous

• Thread View
• Flat View

The problem is ...

The network time sync is ALWAYS in UTC. The UTC knows nothing about daylight savings time. Your system, which does know about daylight savings time, automatically interpolates the UTC standard time to the 1) appropriate time zone (local time), and 2) iterpolates that to either Standard Time or Daylight Time through a mathmatical process. But if the database in your system is incorrect, no amount of time syncing is going to correct the problem. In the Unix world this is all modular and the whole system time resolution is handled by one datafile known as /usr/lib/zoneinfo. When you fix that file, the whole system and all its applications are served with the correct time data. Windows however, still interpolates time through a maze of integrated software fabric, and, unlike Unix type systems, still relies heavily on the bios clock. Unix type systems compute time externally to the bios clock and infact reset the bios clock (which tends to drift) on every shutdown.

Posted by: George Mitchell   Posted on: 03/06/07 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now
• The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... Download Now
• Building the Virtualized Enterprise with VMware Iinfrastructure VMware VMware virtualization software has been adopted by over 120,000 enterprise ... Download Now