Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site necis.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!wanginst!vaxine!encore!necis!yde
From: yde@necis.UUCP (David Elins ext. 220)
Newsgroups: net.bugs.usg
Subject: Re: System V cron problem (with fix)
Message-ID: <219@necis.UUCP>
Date: Thu, 23-Jan-86 10:23:38 EST
Article-I.D.: necis.219
Posted: Thu Jan 23 10:23:38 1986
Date-Received: Mon, 27-Jan-86 03:09:15 EST
References: <405@wlbr.UUCP> <491@whuts.UUCP> <409@wlbr.UUCP>
Reply-To: yde@necis.UUCP
Organization: NEC Information Systems, Acton, Ma.
Lines: 15
Summary: 

In article <409@wlbr.UUCP> jm@wlbr.UUCP (0000-James Macropol) writes:
>
>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.

I can't speak for other systems, but LOGNAME is not passed on by cron
on our 5.1 SysV68 machine. This was the source of a nasty bug in uucico
(this missing LOGNAME was compounded by a coding error in the uucico code).

A shell script run by cron on our machine showed the following environment:
===== environment / Thu Jan 23 10:00:15 EST 1986 =====
TZ= LOGNAME= SHELL= HOME= PATH=/bin:/etc:/usr/bin

david