This is how I understand it from a Sysadmin view. You would think that if you use a date() system call. In PHP you would use string date ( string $format [, int $timestamp] ). So if that is using the X Unix like OS epoch to resolve the date. Then you check to make sure your systems spits this example output..
usr/share/zoneinfo/PST8PDT Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0 gmtoff=-28800 /usr/share/zoneinfo/PST8PDT Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1 gmtoff=-25200 /usr/share/zoneinfo/PST8PDT Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1 gmtoff=-25200 /usr/share/zoneinfo/PST8PDT Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0 gmtoff=-28800 You should be fine. Now if your application is using some other method to figure out what date is. I would say our screwed. Bob you a senior level programmer, so let me know if I'm full of crap. So the question I have is your Windows system patched? If so why is the "meeting scheduling apps " not using a Windows API to pull the date? ( If there is one ). I think this is going to hit the health and medical people the most. There is a massive amount of embedded equipment in the medical field.
From the telemetry systems that monitor vital signs, all the way down
to the pharmacy prescription dispensers. Another area that will be hit unless they started thinking about this back in 2005 are the billing systems. It may not be that much of a mess but I would expect your bills to be late and or some automated call telling you that your behind on some payment. Then again if Bob is having problems with his Windows based meeting app. I would expect Windows cash registers and ATM machines to have problems. So I would get some cash out before the time switch. -Miller _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
