Re: Oninit from cron leaves engine in permanent fast recovery

On Thursday 06 October 2005 12:25, you wrote: > Thanks for the responses. > > Including a 'c' in the shutdown doesn't make any difference Dave ... > sadly. I have tried flushing, forcing, advancing, clearing shm ... all > to no avail. > > There are no relative paths referenced in the script. It's all very > explicit. The script has been executed from different staring points. > > I don't know about open file descriptors Jonathan, but I will find out. > There is no input and output is redirected to a log file in both > cases. Did you redirected stdout _and_ stderr of your script to a file? your_script > /tmp/cron.log 2>&1 Otherwise try additional redirecting for commands of your script, e.g. ... /usr/informix/bin/onmode -yuk > /tmp/onmode.log 2>&1 ... /usr/informix/bin/oninit -v > /tmp/oninit.log 2>&1 Andreas > > I'm not sure what to draw from the fact that it hangs on the temp space > initialisation either ... but it would seem like a clue :) There is, > however, nothing apparently wrong with the spaces. > > Thanks for the suggestions. sending to informix-list