Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site wlbr.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!mhuxt!mhuxr!ulysses!allegra!mit-eddie!genrad!decvax!decwrl!nsc!voder!wlbr!jm
From: jm@wlbr.UUCP (James Macropol)
Newsgroups: net.bugs.usg
Subject: Re: System V cron problem (with fix)
Message-ID: <409@wlbr.UUCP>
Date: Mon, 20-Jan-86 12:35:46 EST
Article-I.D.: wlbr.409
Posted: Mon Jan 20 12:35:46 1986
Date-Received: Thu, 23-Jan-86 08:29:20 EST
References: <405@wlbr.UUCP> <491@whuts.UUCP>
Reply-To: jm@wlbr.UUCP (0000-James Macropol)
Organization: Eaton IMS, Westlake Village, CA
Lines: 18
Summary: cron does NOT set up TZ

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
Eaton IMS
{ihnp4,scgvaxd,voder,vortex,trwrb,jplgodo}!wlbr!jm