Getting clocked by the 'daylight saving' bug
628852
Setting the clocks ahead comes early this year. Are your gadgets and applications ready to spring forward?
628025
This weekend's early switch to daylight-saving time was billed as a little re-enactment of the Y2K computer problem at the turn of the millennium. And as it happened, the daylight bug appeared to have equally minor results.
531889
Techs scramble to update software as Sunday's early switch to daylight-saving time threatens to spring computer systems forward into glitchville. By the Associated Press.
265104
Yankee imperialist time zone go home Venezuelan prez Hugo Chavez today postponed a scheme to secure his place in the pantheon of classic comedy Latin American despots by shifting back his country's clocks half an hour, Reuters reports.â¦
360396
Y\\u2009es, this is 2007. Don't adjust your clocks - not yet anyway.  You didn't wake up this morning back in 1999, once again facing the Y2K scare. Though, as the new earlier daylight-saving time starting date approaches, it may feel more and more like it.
383301
With Daylight Saving Time going into effect this year on March 11, IT vendors are scrambling to prepare patches, work-arounds and other fixes for their products. Here's what some major vendors are doing.
645065
At Computerworld's Premier 100 IT Leaders Conference, a large percentage of the attendees indicated that their companies are still working to prepare for next Sunday's earlier-than-usual start of daylight-saving time.
655672
Some physicists are creating a revolution in the arcane world of ultra-precise clocks. And among them is a researcher who has trouble getting anywhere on time.
70113
-- This weekend's early switch to daylight-saving time was billed as a little re-enactment of the Y2K computer problem at the turn of the millennium. And as it happened, the daylight bug appeared to have equally minor results.
630000
Earlier than usual switch to daylight saving time causes some snags, but no major disruptions are reported.
278695
Daylight Saving Time will arrive this year earlier than it has in the past -- at 2 a.m. on March 11. Companies are scrambling to make sure their IT operations will be ready.
148167
QMy PC now flashes a start-up message from a company called "Phoenix"; hitting the F1 key gets me past this, but my other problem is that the computer keeps thinking that it's 11:01 p.m. on Dec. 31, 2002 .
510930
The new law turning clocks forward earlier may wreak havoc and has businesses struggling to make costly fixes. And it's not even certain the move will conserve energy
749368
Customers using Microsoft products that have entered their "Extended" support phase will need to fork over $4,000 for a patch that makes the software compatible with the new March 11 date for Daylight Saving Time (DST), according to Microsoft watcher Mary Jo Foley.
274935
Normally the switch to daylight-saving time isn't a big deal, but this Sunday, Jeff Ronner has to put people on the case.
252573
By Daniel Patrick SheehanAs any science fiction buff can tell you, no good can come from fiddling with time. Alas, Congress did it anyway, by extending daylight-saving time.
612406
(InfoWorld) - The new DST (daylight-saving time) is drawing near. Do you think you're ready? Run down this checklist to be sure. 1. Do a datacenter inventory. You need to know exactly which applications and systems you have running so that you can locate appropriate patches and fixes. 2. Find out what needs to be patched. That could take some time. Fortunately, many of the big-name vendors have prepared (even if you haven't). Below is a list of DST resource sites for various companies. Most, if not all, include lists of solutions that will be affected. Apple BlackBerry Cisco Dell Hewlett-Packard IBM Microsoft McAfee Novell Oracle Palm Red Hat Sun Symantec Also be sure to update your JRE (Java Runtime Engine), as apps running on older versions of JRE may report incorrect times. Info is available here. If one of your vendors isn't listed above, check out their Web site or call their help desk as soon as possible and ask about DST patches. 3. Devise a game plan. Mission-critical, time-sensitive applications should take priority, but also consider software -- such as firewalls -- that isn't time sensitive but that feeds time-sensitive information to other programs, such as security event management products. 4. Deploy patches or, where necessary, manual fixes. Use your centralized software management toolbox such as Microsoft Systems Management Server or Novell ZenWork Patch Management (if you have one). Otherwise, you'll have a lot of manual patching to do. 5. Test your patches and fixes. Be certain you come up with proper times and dates. You also have to check that your applications are interacting properly. 6. Make sure your partners and service providers are prepared. Just because you've done your due diligence and updated your systems doesn't mean one of your critical suppliers, for example, has. 7. Schedule IT personnel to come in on March 11. Try as you might to prepare, it's entirely possible something will slip through the cracks. Have IT staff on hand to check the status of systems, run tests, and fix problems.