Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucsdhub!jack!man!nusdhub!rwhite
From: rwhite@nusdhub.UUCP (Robert C. White Jr.)
Newsgroups: comp.unix.questions
Subject: Re: How to set TZ for cron?
Message-ID: <165@nusdhub.UUCP>
Date: Tue, 20-Oct-87 21:19:10 EDT
Article-I.D.: nusdhub.165
Posted: Tue Oct 20 21:19:10 1987
Date-Received: Fri, 23-Oct-87 01:42:53 EDT
References: <290@etn-rad.UUCP> <1588@macom1.UUCP>
Organization: National University, San Diego
Lines: 22
Summary: Our 3B2 and cron with TZ.

In article <1588@macom1.UUCP>, michael@macom1.UUCP (John Michael Mullins) writes:
> in article <290@etn-rad.UUCP>, markus@etn-rad.UUCP (Markus N. Richardson) says:
> > [Timezone Problem in AT&T UNIX]
> [An echo of the above, with refrences to bad Customer service]


	Our [the only one at the time] 3B2 had the same problem.
I work fairly closley with some AT&T people, and was told that
the cron thing had been overlooked for SVR2 or below.  The newest
releases SVR3.1 [I dont know about 3.0] support TZ Correctly.  There
were several TZ munges in cron.  As near as I could figure, the older
cron just does not deal with it's environment at all.

My fix was to prepend . /etc/TIMEZONE ; to every cron line and add
three hours to the hours field [when used]  It's ugly, but the
programs [especially uudemon.hour (as in poll)] appreciate the
prepend greatly.

[Now if only the one vendor we are having problems with would
certify a 3.0 or better release of it's software]

Rob.