I've been poking around some, figuring out how things run under PAR, and I found the cause of my problem.

I'd done an 'su' to root to set up the environment, since it includes an Oracle lib directory that needs to be configured with 'ldconfig'. I then ran one of the scripts (I don't, at this point, remember whether it ran or not - I suspect not, though). In any case, the 'cache' created in /tmp was named based on my login name (par-rmcgowan) but was owned by root, as were all the files in it. This is the cause of the problem, since removing the /tmp/par-rmcgowan directory and then running one of the scripts as myself, resulted in a new cache directory, owned by me, and successful execution of the script.

Thanks to you all for taking a look and prompting me with ideas to check out.

Bob

Mark Reboul wrote:
Here is something.  Maybe not very much.  The only reason I offer this is
that the verbiage ""No such file or directory at -e line" happened to me
once in PAR context.  I posted the problem at

http://www.mail-archive.com/[EMAIL PROTECTED]/msg01315.html


FWIW, I reported similar looking failures in --


http://www.mail-archive.com/[EMAIL PROTECTED]/msg01520.html


I reported them on AIX (supported) and IRIX (unsupported).

I was able to obtain such failures on Linux too, though it required my inflating the env size to outrageously high values.

-- Mark





Reply via email to