Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: TZ command under sr10.3 Message-ID: <9104032251.AA19047@pan.ssec.honeywell.com> Date: 3 Apr 91 22:51:58 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 38 > A week ago, I posted an article asking for help with the TZ command. > I recieved a couple of usefull answers, but my problem persists. > > % tz edt <---- Change the timezone > % /bin/date <---- Check the date, and it's wrong > Wed Apr 3 15:46:06 EST 1991 > % tz <---- Verify the timezone > Timezone: EDT > Delta from UTC: -4:00 > > However, the date command under /com will work correctly. > > Does anyone have any ideas on how to fix this? Or, does the bsd4.3 date > command simply look at a different clock? This same problem was discussed last year about this time (funny how that works). :-) As I understand it from the previous discussion, the problem is that Unix decides to be 'intelligent', and try to figure out Daylight Savings Time for you. Both Aegis and Unix use the same clock -- it's kept in UTC, though. Aegis applies the timezone offset to get the local time, and will never second-guess you. Of course, this means that Aegis will not automatically change over, either. You need either a cron script or you run around early Sunday AM changing the 'tz' everywhere. Unix, apparently, tries to figure out when daylight savings time goes into effect, and changes over at that point. The tz command does nothing for it except to get the actual zone (not the particular offset for daylight/standard time). This might be fixed when you reboot (I can't remember for sure), but it definitely isn't dynamic like Aegis is. (Yet another example of the inate superiority of Aegis over Unix! :-) -- jt -- John Thompson Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com Me? Represent Honeywell? You've GOT to be kidding!!!