Re: 4gl Program's Parent Dies, Child Continues

In article <560tcd$kn1@news.bayarea.net>, "Paul J. Mantyla" <paulm@bayarea.net> writes > >I've been unable to find a solution to this problem in the International >Informix User's Group FAQ. I'm hoping that this is a well-known problem >with a well-known solution. > >We have a compiled 4gl program which runs another compiled 4gl program. >Both the parent process and the child process are interactive. If the parent >process is killed, it seems as if both the underlying shell (ksh) and the >child process try to claim the terminal, resulting in an unusable terminal. Strange, I'm not sure about this one. Shouldn't the parent wait for the child to finish? You can not have two interactive programs running on the same terminal at the same time. >If the shell process is killed, the child process continues. However it >has lost it's terminal and goes into and infinite loop, consuming 100% of >the cpu on the system. That is a known bug in 4GL - fixed in recent versions. > >Is their a special way to start child 4gl programs to prevent this sort of >behavior? (Through an external C function?) > Not really - you should not get into this situation, sounds like you need to upgrade your 4GL. >If it matters we're running on an HP-UX system, I don't know which version. > > >-- >Paul J. Mantyla >paulm@bayarea.net -- David Williams