RE: Oninit from cron leaves engine in permanent fast recovery

You might want to check your script and make certain that the line: #!/bin/ksh is the first line in the script, no blank lines before it. That line specifies that the script be run in the Korn shell, but only if it is the first line. Otherwise it is ignored as a comment. Since jobs executed from cron run in a Bourne shell, this may be causing your problem. I don't see anything in your posting to support that, but it is worth a mention. Regards, Bill > -----Original Message----- > From: owner-informix-list@iiug.org [SMTP:owner-informix-list@iiug.org] > On Behalf Of gerry.cassidy@dsl.pipex.com > Sent: Thursday, October 06, 2005 6:26 AM > To: informix-list@iiug.org > Subject: Re: Oninit from cron leaves engine in permanent fast > recovery > > 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. > > 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