Re: Revived: Oninit from cron leaves engine in permanent fast

Hi Jonathan Thanks for replying. I did try the suggestion with full output redirection, i.e. oninit < /dev/null > /dev/null 2>&1 & This made no difference to the state of the instance when started via cron. The environments for cron and command line execution have been thoroghly compared, line by line, and there is no difference. There may be something lurking deep underneath in the AIX layer. I am assured that this is not the case by system administrators, but you never know! I have not tried setting a simple cut-down environment. I will give this a go. We now have Liesel Bach working on the problem from the IBM side (and now you also :). I am waiting for dbx requirements from Liesel as she has requested further information. I have also been trying to organise a dial-in capability but have hit a big brick security wall here and so it is not allowed. Next step is to request an engineer on site! We do have lsof installed so I will replicate the problem and post or send you the lsof output (if that's okay with you). Thanks again. This is a weird one. Regards, Gerry PS Dave - the problem I was having with background was playing around with getting a foreground oninit -d to finish or go into background. I can of course run oninit & but what use?