Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site whuts.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuts!paul
From: paul@whuts.UUCP (HO)
Newsgroups: net.bugs.usg
Subject: Re: System V cron problem (with fix)
Message-ID: <512@whuts.UUCP>
Date: Mon, 27-Jan-86 13:50:40 EST
Article-I.D.: whuts.512
Posted: Mon Jan 27 13:50:40 1986
Date-Received: Tue, 28-Jan-86 06:31:07 EST
References: <405@wlbr.UUCP> <491@whuts.UUCP> <409@wlbr.UUCP>
Organization: AT&T Bell Laboratories
Lines: 26

> In article <405@wlbr.UUCP> I write:
> >> System V r2v2 cron neglects to set up the TZ variable in the environment.
> In article <491@whuts.UUCP> paul@whuts.UUCP (HO) writes:
> >If you set TZ before you start the cron, and export TZ, then you don't 
> >need to change the cron. You can do this in /etc/rc, assuming cron is
> >started there.
> 
> This is not true.  cron does NOT pass its environment along to any invoked
> program, but constructs an artificial environment, containing only HOME,
> LOGNAME, PATH, and SHELL.  Note that TZ is left out.  In order to pass TZ to
> invoked programs, two things must be done:
> 
> 	1) TZ must be set up and exported in the /etc/rc file.
> 	2) cron must be modified to pass TZ along to invoked programs.
> 
> Jim Macropol

You are right and so am I. I looked at the source, and cron was 
already modified to use TZ. For me, I don't have to change the cron,
since we use Bell Labs Division 452 UNIX, and it seems our UNIX
is a little ahead of the official public release. I would *assume*
that bugs like that will eventaully find their way to a later release.

Paul Ho

*** REPLACE THIS LINE WITH YOUR MESSAGE ***