Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!cernvax!cernapo.cern.ch!rtb From: rtb@cernapo.cern.ch (Rainer Tobbicke) Newsgroups: comp.sys.apollo Subject: Re: TZ command under sr10.3 Keywords: daylight time tz Message-ID: Date: 16 Apr 91 10:41:04 GMT References: <350@galileo.rtn.ca.boeing.com> <50ef33dd.3593b@digital.sps.mot.com> Sender: news@cernvax.cern.ch Lines: 24 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. 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 /bin/sh users, but not /bin/csh. Also, I feel that when I 'crp -me' to a node TZ should be set which does not seem to be the case. 'man login' claims that TZ will be initialised, but if that is true then it's initialised to "" ! Some help file claims TZ is initialised from what's recorded on the disk. Rubbish! (at least under 10.3) Any ideas? -- Rainer Toebbicke European Organisation for Nuclear Research (CERN) Geneva, Switzerland rtb@cernapo.cern.ch, rtb@cernvm.cern.ch