System V cron problem (with fix)

[David Elins ext. 220]

In article <409 at wlbr.UUCP> jm at 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