Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!oakhill!nddsun1!digital!digital.sps.mot.com!chen From: chen@digital.sps.mot.com (Jinfu Chen) Newsgroups: comp.sys.apollo Subject: Re: TZ command under sr10.3 Keywords: daylight time tz Message-ID: <51086ab5.3593b@digital.sps.mot.com> Date: 17 Apr 91 20:14:23 GMT References: <350@galileo.rtn.ca.boeing.com> <50ef33dd.3593b@digital.sps.mot.com> Sender: news@digital.sps.mot.com Organization: Motorola, LICD, SPS, Mesa, AZ Lines: 26 Nntp-Posting-Host: logic In article rtb@cernapo.cern.ch (Rainer Tobbicke) writes: >Related to this: has anybody got an idea on how to introduce >the TZ environment variable into every process and it's >children? In any Unix environment it does not make sense to >mess around with /com/tz every 6 months, since TZ can handle all this quite >well a la POSIX. I believe the TZ (and TZNAME) environment variables are set automatically in the Unix environment, at least in US. It's the automatic setting feature that really bugs us who live Arizona (we don't have summer saving time). What I ended up doing (learn from suggestion in comp.sys.apollo long time ago) is to add the TZ and TZNAME in /etc/rc and /sys/node_data/startup.* files so we always have the right timezone setting. >Only: it assumes that the TZ environment variable is always >present. I wouldn't mind rebooting once (!) for this. >I tried setting it in /etc/rc, where at least all inetd >children seem to get it. But things started by /etc/init e.g. >from /etc/ttys (like the DM) do not. /etc/TIMEZONE helps for Try setting TZ in /sys/node_data/startup.*, such as in our /sys/node-data/startup.1280color file: # to defeat automatic summer saving time ENV TZ MST7 ENV TZNAME MST