Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!granite.pa.dec.com!mellon
From: mellon@nigiri.pa.dec.com (Ted Lemon)
Newsgroups: comp.unix.ultrix
Subject: Re: HELP!!!  cron bugs
Message-ID: <MELLON.91Jun27143758@nigiri.pa.dec.com>
Date: 27 Jun 91 19:37:58 GMT
References: <14264@goofy.Apple.COM>
Sender: news@pa.dec.com (News)
Organization: Digital Equipment Corporation
Lines: 14
In-Reply-To: erc@Apple.COM's message of 26 Jun 91 18:21:18 GMT


Hm.   I'm using Ultrix cron quite happily, and have never run into the
problems you've mentioned.   The main wins about Paul's cron have to do
with featurefullness, not with basic functionality.

I wonder if you're setting your path in your shell scripts?   I've run
into problems from time to time where I test a shell script while
logged in, and it works just fine, but when I run it from cron,
nothing happens.   In every case, it's been because I assumed that I'd
get the same path from cron that I normally get when I login.   In
fact, /usr/ucb isn't present in the path you inherit from cron, and
some other things you may assume are present also are not.

			       _MelloN_