Poll: The final word on DST

Poll: The final word on DST

Summary: From most indications--the Daylight Saving Time change--passed without any major hiccups. Computerworld sounded the all clear.

TOPICS: Tech Industry

From most indications--the Daylight Saving Time change--passed without any major hiccups. Computerworld sounded the all clear. And aside from a few issues the time change didn't cause any major IT issues.

Take a bow since you IT folks were the ones to make the transition happen. However, color me just a tad skeptical about the smoothness of the DST change given the amount of email we were bombarded with. Here is an informal series of polls to shed light on how the DST switchover really went.

[poll id=54]

[poll id=55]

[poll id=56]

[poll id=57]

[poll id=58]

[poll id=59]

Topic: Tech Industry

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Amazing

    It amazes me that these companies knew about the DST change back in 2005 and waited until the last minute to get their patches out. Microsoft being one of the worst offenders rolling patches barely 2 weeks before the DST change for some products. Some products like tzmove having 6 or more revisions to fix bugs.

    Could these patches have not been created and tested before the end of DST last year? Then rolled out to customers within one week after the end of DST 2006? Yes is the correct answer to both.

    With 1.5 years of notice this could have been far better executed.
  • Not a fanboy

    I am not a Linux zealot, but I have to say that CentOS (Red Hat) had by far the best DST support.

    1. The DST changes were just a couple of lines in a config file. Maybe hindsight is 20/20, but I can't understand why so many vendors hard-coded DST into their apps.

    2. The DST fix was available months ago.
  • None of the above

    [i]Did all of your DST vendor patches work as expected?[/i]

    No patches, no expectations, thus I suppose you could say "yes."

    [i]Have you patched everything that was necessary for DST?[/i]

    I didn't do any patches, but that was all that was necessary.

    [i]What vendor had the best DST support?[/i]

    Mother Nature.

    [i]Were there DST patch conflicts?[/i]

    I can say with absolute certainty that there were none.

    [i]Were you ready for the DST change by?[/i]

    1 January 1970.

    [i]What vendor had the best DST support?[/i]
    [i]What vendor had the worst DST support?[/i]

    Same answer to both: don't know, don't care.

    Bottom line: neener, neener!
    Yagotta B. Kidding
  • IBM was excellent/M$ sucks

    I got notices months ago about the PTFs needed to correct the problem on our iseries server. M$ gets the big 0 for charging $4000 for a simple patch on older OSs. As if 2000 server is really that old in the business community.
    • the 4000 was just for cdo components on exchange 2000....

      as far as i know their isn't a patch for windows 2000.

      however you can roll out a patch easily to 1000's of servers with little effort, I did.

      and 2000 Server blows.
      • Patch for 2000 server

        The $4000 would've got you a patch for 2000 too (I believe) but considering it was just a copy and paste of some scripts and registry changes from the KB article to fix DST, why bother.
    • IBM, Sun, and Microsoft were all bad

      Sun was releasing Java patches as late as Friday, I've got meetings scattered all over my IBM Lotus Notes calendar (no rhyme or reason, some fine, some ahead, some behind), and when the Microsoft Windows patches were pushed out to end users many had their observe DST check box unchecked. So why is my company paying big bucks to these guys over open source alternatives again (Java's free but we run Sun servers as well)? Oh, that's right, for support and reliability. As if.
    • IBM APAR's worked fine at my site as well

      I give IBM high grades w/ DST. I would also give high grades to Sun and HP as well. Our main issue was w/ MultiNet on OpenVMS (which unfortunately our biggest app is on these boxes for our hospitals). We also had a few app vendors that had issues w/ their patches.
  • Only real problem was SCO

    Windows machines updated fine, using either the XP SP2/2003 patch or the registry patch posted in the KB. No worries. Our OpenServer 5.0.6 I had to change manually. SCO offered NO support for anything pre 5.0.7. This server is scheduled to be retired soon so an OS upgrade wasn't worth it for a DST change. Chalk up another thumbs down for Caldera. If SCO were still SCO I'd like to think support would've been better.
  • Too early to tell!!

    Is noone else thinking what I'm thinking? That it's too early to know if all is good? Maybe the patches made our computers and electronics forward an hour on the new date...but don't we need to get past the old DST date before knowing that there is no glitch? Seems likely that at least somewhere, there will be some electronics that will try to do a DST change again on that date....
    • i was wondering the same

      what actually happens when the normal DST comes around? Are the pc's going to try and update the time an hour ahead again? Anyone know if he patch for MS will keep this from happening?
      • Shouldn't ...

        If I understand correctly, the patches and time zone editor tool changes the databases for the time zone database and time zone information database in the control set. So I think there is not any old DST because that has been modified. As for nixes there's a conf file for DST (If the file is modified then there is not an old DST on nixes).

        So it's good that you're concerned and should be I just think the question is a little off base but please correct me if I'm wrong.

        For everyone that rags on others about the Windows guys, it really isn't about changing a clock what's so hard about that--but that the cdo files have to be updated and unless you paid 4000 for those updates you have to be concern about Exchange 2000.

        As another poster said it is a PITA on GP.
        • sounds good to me...thanks(NT)

  • Zero problems with any of our Macs. [nt]

    • No Problems on Windows either

      Actually it all worked fine.

      The biggest pain was SUN boxes and Cisco routers and switches. Not that they were hard but SUN's website is brutual to navigate to get the patch. Too me two days to find, login and download it. This obsoleted by that obsoleted by that. Finally find and you need to log in. Then my password wouldn't work. Had to have reset and it took for ever to show up. Then I type in the patch number I found it brings up nothing. I had to go through link on a obsoleted patch. SUN really ticked me off that day.
  • no probems here

    No problems for the Mainframe. Of course the boys over on the distributed side of the shop have been jumping through hoops, they setup a commander center to coordinate all those patches and update all the notebook PC's and now y'all are worring about what happens when the "real" DST day hits, gee maybe more patches needed. Too bad, So sad.
    • Mainframe needs IPL to change TIME

      So I guess that's not a problem
  • dst issues

    IBM's support worked best for me.
    Any chance GoDaddys supposed denial of service was a DST problem? Their claim they did not need to do anything because they are in Arizona (no time change) doesn't mean all their hardware & software was "ready". Others I heard from today were having to reboot some routers before they worked & perhaps that is their "denial attack...".
  • DST

    3 computers with auto updates---no problems
  • Biggest problem was with applications

    Microsoft, HP-UX, Solaris, and Oracle updates went fine. We had some applications that either didn't have a patch and were known to not be compliant, or the application still had the incorrect time stamps even though the OS and application was patched.

    Nothing was a show-stopper but we still had more issues than during Y2K.
    Uber Dweeb