Script Works, But Not with CRON

[Bill Vermillion]

On Tue, May 04, 2004 at 11:06:00AM -0400, Bob Stockler thus spoke:
> The following script works _perfectly_ when excuted from
> the command line, but fails when run by 'cron'.

> I added the statements "STATUS=${STATUS}$?" after each
> filePro command to capture the exit values of each one,
> and it returns "STATUS=101011" in email to me.  That
> indicates all of the filePro commands except the "ddir"
> one are failing.

> No other filePro processes are running when this is run.

> What am I overlooking?

'ddir' runs SUID as root.

To me that indicates it could be permissions problem along the
line, or it could be the user executing the cron jobs.

What version of *n*x are you using this script on.

Is it one that has separate crons for each user, or is it one that
puts everyting in one big pile.  If the latter make sure that the
correct user is running the programs.

Any errors in your cron log.  Ensure you you don't run the 
command with errors going to /dev/null until you get it working.


-- 
Bill Vermillion - bv @ wjv . com