Slashdot Mirror
Preparing Your Datacenters for DST Changes?
Cheeze asks: "As I am sure some of you know, Daylight Saving Time is slated to change this year thanks to The Energy Policy Act of 2005. This means nothing to the large majority of the population except they will either sleep late one day or have to commute in the dark. To a select few, this is a crunch time akin to the Y2K fiasco, only there has been almost zero publicity recently. These select few are the ones responsible for updating the millions of computers, both servers and workstations, with the new time zone information. For newer servers, this usually means just install a patch and reboot (which is slightly more than mildly inconvenient). For older servers, this is basically an 'End of Life' declaration. Servers running software for which no patch is available will be unable to update their own clocks. This doesn't seem like such a big deal until you realize Microsoft is only offering patches for Windows XP and beyond, and Sun will not be supporting Solaris 7 and older. That should knock a large percentage of the computers 1 hour off for a few weeks this spring. What are you doing in your datacenters to prepare?"
..that your servers don't use GMT?
Using UTC.
In the US, move your servers to Arizona or eastern Indiana or Hawaii or Alaska, so you don't have to deal with time zone changes anymore.
-ez
I'm more concerning of a switch back to the old DST (the one we had in 2006) if they decide it's the energy saving isn't good enough. How difficult would it be to unpatch out systems?
There is no reason for having a single server clock on non-UTC. DST, even if it was to stay the same forever, makes things a pain in the arse (once a year, an hour happens twice).
Your client should convert the timezone. For a client machine, it's not much hassle just to go into clock settings and change it.
Worst case is web-apps - the server clock should be UTC, but you still need to convert the time zone in the client-facing PHP/Perl/Java/etc code. There you're just looking at a patch to the language runtime or whatever.
I just got my servers switched over from the Julien to the Gregorian calender. Now this. When will it ever end.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
This should fix the problems for your Unix based machines. You can download a set of time zone source files from ftp://elsie.nci.nih.gov/pub/, these files are in the public domain. From these files you can build a full set of zoneinfo files (read the man page for zic(1)), DON'T FORGET TO BACKUP YOUR CURRENT ONES IN CASE OF PROBLEMS!! For most Linux based distros this is in a package called tzdata (which will compile the source files into zoneinfo files for you). zic(1) should put the compiled files into the right directory for you. These source files should work with most zic(1)'s, if not you may need to massage them with sed or perl. Don't forget to update /etc/localtime (or whatever other mechanism your OS uses, /etc/timezone et al) to set your localtime to the right zoneinfo file.
Mod parent up. ISTM that you're better off if all computers have their hardware clocks set to UTC and the conversions to local time take place at the last possible time in the clients (if at all). If a user wants to use some client software or OS that doesn't understand the silly daylight savings rules (which are extremely crazy in some places); at least they don't damage anything in the datacenter and will only confuse themselves.
OTOH, what kind of evil company won't even give as trivial a patch as updating a time-zone file to their customers!?! If I had any such software and the company still existed I'd be wanting a full refund.
"...Microsoft is only offering patches for Windows XP and beyond"
They are offering support for Windows 2000, free with the right volume license, $$$ without, or they have made a manual registry hack available (which I don't have handy because I'm posting from home).
And before you ask, there are companies that still specify Win2K server and workstation to run their software, Thompson/Prometric being one of them, which is how I came to find this out.
Some days it's just not worth
chewing through my restraints.
I only had to chance it once (on Win98 if I remember correctly) and there it was just an regedit call. No reboot required. At this time Win98 was switching the DST about a month wrong in MET, and I had to correct that. There is also a Microsoft Utility called tzedit, which displays and modifies the time zone rules. To have it affect the displayed time, you can go in the Control Panel, choose Date & Time and hit Ok. Then it will refresh the timezone information according to the changes you made with the tzedit.exe utility.
A more complete description of the necessary registry changes is at
Microsoft Knowledgebase 914387.
But as someone already wrote in an earlier post: Set your servers to use NTP, either from your local nameservers or from *.pool.ntp.org and have it automatically adjust for DST.
Thats a good idea, but won't always solve all of your problems. Here's a problem I experienced recently with one of our web apps.
We have a web event calendar where people can schedule events (for far into the future). When people input an event, they specify the date/time it will begin/end. The application then converts the date/time into a unix timestamp and stores it in the database. Later, when an event is being viewed, the timestamp is converted back to a textual date/time.
The conversion from local time to timestamp is done via PHP functions, which uses the systems timezone file. The OS patch to fix this problem simply updates the timezone file and everything should automatically work.
This is fine and dandy for most things, but I ran into one small glitch. For any events that are scheduled between the new start of DST and the old start of DST (roughly a 3 week period), if they were created BEFORE the patch was applied, they are now off by 1 hour AFTER the patch is applied.
The 1 hour difference is simple enough, and I might not have even noticed...or if I had, I probably would have just blamed it on user error when entering the data. However, this caused a strange side effect. The application built a secondary index to simplify searching for events. The index consisted of the event_id and the starting timestamp truncated to midnight. Of course, for those events in that 3 week period that were created before the patch was applied, they now had an index timestamp that was actually 1 AM. Of course, this caused events to mysteriously disappear from the calendar. You could search for them, but not see them when browsing.
I wasted a good couple of hours on this problem (thinking at first that it was isolated to a single event) before I finally did an analysis of the entire index and discovered that almost all events in that 3 week period were wrong. Then it instantly dawned on me what had happened.
OS patches are easy - we even built our own for patches for some obsolete unix flavors. The tzfile format is well documented and straight forward.
Our big issue is java... Whoever designed that piece of sh*t should be shot. They get the time information from the OS - so why not pull the TZ data from the OS too? But no - they rather implement it themselves... The result is beautiful. Oracle installed? You need an extra patch. Informix 10? Another patch. Websphere? Guess what - patch it separately! In the end, we had some boxes that needed 8 or more applications patched in addition to the OS.
Peter.
Clock companies everywhere aren't prepared for this. I work for one and they have to manually update all of the tower and post clocks that they have made which is in the thousands. When this last happened in the 70's there weren't embedded electronic clock systems. When daylight savings time came around you just got up on a ladder and spun the dial backwards. CBS had the best quote on this from there nightly news "do you love summer barbeque's and parties? then you'll love this" almost like they were selling the story back when the first passed the bill.
I don't think you work in a datacenter then. Once our servers are configured and running, there should NEVER be a reason to reboot them. In fact, when we have an odd server failure, the server usually has been up since it was first put in the datacenter. We are just now getting failures of systems put up in the late 1990s. Sure we have new systems as well, but there are critical systems still running old hardware because it works and a reboot is too much of an outage to take.
If you don't think it could be inconvenient to patch and reboot hundreds or thousands of servers, I don't think you are looking at the whole picture.
That vague possibility of some embedded systems being thrown away include, vcrs (good riddance), DVRs, watches, GPS devices, car computers, phone systems, just about all networking gear, etc. These are things that will either need a software upgrade or a hardware upgrade within the next 3 months if they are to give the correct time.
Why read the article when I can just make up a snap judgement?
Out of deference to the events in 2001, the number 911 should be reserved for unique use (in North America) of the emergency services telephone number, it's use in all other contexts... 13 could be included in the ban to standardize current practices. Most high rises do not have a thirteenth floor, and Friday the 13th would cease to be a problem. No price, by law, for any item will ever be 13 or 911 dollars, except on march 13th (except when that would fall on a friday, in which case it would be a slip year), and September 11th, when those prices will be allowed. No use of the numbers 13 or 911 will be permitted in architectural or engineering diagrams of any kind, for fear offending those who lost loved ones on that terrible day.
The impact on counting should be very minor, as I personally lived in an apartment on 12B for many years, and there was no cost to this. A few if statements here and there. Sure, there are some complications,
Look, for example at the daylight savings time, how simple it is to understand that on some days of the year, there are 23 hours, (where there is no 3:12 am.) and on others, there are 25 hours (where there are two 3:12 am's.) but only in some places, sometimes, depending on what the local government says.
It is great to change how people count... dollars, dimensions, hours, to serve political or societal goals. It makes life better for everyone. Much simpler than changing prices or opening hours to serve them. All we need to do is pass a law, and change the way we count. Simple and practical so that no one has to keep track.
Timezones have outlived their usefulness. They were a great improvement over every village setting it's time as before timezones existed, but nowadays, you never know when something is on tv (except using an electronic program guide) and there is so much long distance interaction (ie. tech support in India, R&D division in China, etc...) that telling time has become a real hassle. If you work in a company of any scope, there are lots of meetings, and many are missed because people didn't notice the timezone, or even if they did, miscalculated the difference between their timezone and this one. Working in Canada, have to deal with: Newfoundland, Atlantic, Eastern, central, Saskatchewan (and a few cities either east or west of it that adopted the no-DST rule) mountain, and pacific time zones.
It would be a heck of a lot easier if folks would just, at a state/province, or some sort of regional level, decided that stores open at 14 Z in the winter, and 13Z in the summer (corresponding to 9am Eastern time, including DST) Store hours are already mandated, so just mandate that they change summer and winter, but do not change how people count. Define 'Local Standard winter hours' and 'Local standard summer hours.' Do not change the clocks, change the times...
I would rather do away with DST entirely, but if you must do it, it should not be done by changing the time, but rather by changing the hours, and keeping time straightforward. The best would be to forget about DST and timezones entirely, and for everyone to adopt UTC.
You should have been around for the BC to AD conversion.
We thought we were going to be fine with that here, as we had some wise men who worked out when they were going to start. We were planning on just using an integer for number of years:positive for AD, negative for BC. However, some idiot politician somewhere decided to start labelling the years at 1 instead of 0, so now we've got an out-by-one bug every time you try to do a calculation that crosses the AD/BC boundary.
When our name is on the back of your car, we're behind you all the way!
Arizona functions well without DST because it's pretty far south, and the length of days doesn't change too much.
For those of us further north, DST is helpful, because having the sun rise at 4am and set at 8pm is wasteful, as most people don't start their days until much after 4, and their evenings certainly don't end at 8.
There was an interesting article in Slate a while ago arguing that it's not DST that should go, but time zones altogether.
Under Unix, you could configure time zone changes yourself with zic.
For example, the following input to zic will create the four zone info files US/Eastern, US/Central, US/Mountain and US/Pacific. These will be under your ZONEINFO directory (mine is /usr/share/zoneinfo).
The input above configures the time change for the years 2007 to 2017 (an arbitrary end year) so that DST starts the second Sunday in March, and ends the first Sunday in November, as specified in the Energy Policy Act of 2005.
You can test your resulting files using the zdump command, like this
You might have to refresh links to these new files, check /etc/localtime.
Disclaimer: I'm not a time zone expert, so don't take this on faith.
Obviously you're not a parent...
I am billdar, and I approve this message.