Script Works, But Not with CRON
Bob Stockler
bob at trebor.iglou.com
Tue May 4 08:43:33 PDT 2004
On Tue, May 04, 2004 at 11:24:10AM -0400, Bill Vermillion wrote:
| 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.
SCO OSR 5.0.5 (the OS is not maintained by me, but by
Tom Parsons, who is _very_ thorough, so I'm sure it is
patched up-to-date).
| 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.
Separate crontabs, and it's being run from root's.
Bob
--
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).
More information about the Filepro-list
mailing list