On Tue, 14 Apr 2009, chris (fool) mccraw wrote: > ah, then you should start the debugging there. add a "set -x" to the top > of the shell script to get verbose output of every command that runs. i > bet you see that some variable is not being set as expected or some > 'setup' part of things is failing and causing the script to "finish" > early, before calling the perl script.
Chris, This supposes that a variable is set sometimes and not all the time. Today's results suggest it's a lot more complex. This morning, my INBOX had the report mailed after the 00:02am run, but not the report for a scheduled run at 04:40am. But, when I manually invoked the shell script from the command line about 10:15am, it ran, too. That's why I wrote it's such a perplexing situation. There appears to be no rhyme or reason to predict when it will work properly and when it won't. Annoying. Thanks, Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
