Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!mimsy!umd5!decuac!macom1!michael
From: michael@macom1.UUCP (John Michael Mullins)
Newsgroups: comp.unix.questions
Subject: Re: How to set TZ for cron?
Message-ID: <1588@macom1.UUCP>
Date: Mon, 19-Oct-87 12:54:28 EDT
Article-I.D.: macom1.1588
Posted: Mon Oct 19 12:54:28 1987
Date-Received: Tue, 20-Oct-87 21:49:12 EDT
References: <290@etn-rad.UUCP>
Organization: CENTEL Information Systems INC.,Rockville, MD.
Lines: 30

in article <290@etn-rad.UUCP>, markus@etn-rad.UUCP (Markus N. Richardson) says:
> 
> 
> We are having problems *encouraging* cron to accept our (PST8PDT) timezone.
> So far we have done the following to try to alleviate the problem:
> [edited]
> None of these have solved the problem.  All cron jobs still execute based
> on the default timezone (EST)!  Any good ideas?

We had the same problem at our site.  This function did work under System III,
but after much phone time with AT&T support, they say the TZ variable is not
a supported function of cron.

My opinion of the situation is that it was intended to be supported, but it's
one of those problem bugs that someone made an executive decision "to let it be"

One of the things I noticed about this bug, or "lack of feature" is that when I
try to set the TZ variable as you mentioned, the actual time reported by the
executed program, is not consistent.  One day it will execute at 2100, report
that the time is 0600, then the next day, it will again run at 2100, but the
reported time may be 0820 (or something equally off the wall).

Unless someone with source knows better, I would say you/we are stuck on this.


-- 
John Michael Mullins
CENTEL Business Information Systems, Inc.
5515 Security Lane, Rockville, Maryland, 20852, (301) 984-3636
UUCP:   michael@macom1.UUCP 	or	decuac!macom1!michael