Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek From: torek@elf.ee.lbl.gov (Chris Torek) Newsgroups: comp.unix.questions Subject: Re: The swich with dailight savings time Message-ID: <12021@dog.ee.lbl.gov> Date: 12 Apr 91 17:02:09 GMT References: <9@phlpa.UUCP> <295@ukelele.UUCP> Reply-To: torek@elf.ee.lbl.gov (Chris Torek) Distribution: usa Organization: Lawrence Berkeley Laboratory, Berkeley Lines: 27 X-Local-Date: Fri, 12 Apr 91 10:02:09 PDT In article <295@ukelele.UUCP> chris@ukelele.UUCP (Chris Linstruth) writes: >I dealt with this problem by setting the hardware clock to GMT ... The is the right way to do it. Another method that is not quite as good, but might be necessary for some people, is to keep the hardware clock on `normal' time: instead of >TZ=GMT0;export TZ >date `/etc/setup -d` > /dev/null >. /etc/TIMEZONE you could (assuming your timezone is EST5EDT, e.g.) use TZ=EST5 date `/etc/setup -d` >/dev/null TZ=EST5EDT; export TZ It is (or will lead to :-) ) sheer insanity to keep internal times in multiple formats, and it is best to use a single agreed international standard for internal times so that all machines can agree as to what time it is. (It is somewhat amusing to watch PC users bump into all the old problems as their systems expand. I imagine old-timers felt the same way about Unix systems when they began to displace `mainframes'.) -- In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427) Berkeley, CA Domain: torek@ee.lbl.gov