Orphaned sql turbo processes.
Posted in 1994
I recently attend an Informix class on system administration, the class instructor claims when we C-ESQL code we need have a signal handler which do a sqlexit(). He claims that if the parent process gets killed then there is a chance that the sqlturbo will be hanging around. But i don't think so, sqlturbo use a pipe to communicate with the parent process, so the turbo process has to receive a SIGPIPE at one time or the other. Even if it ignores SIGPIPE it has to get an error when it tries to read the pipe, because the other end of the pipe is closed. Has anyone had the orphaned sqlturbo processes hanging around? Is there any logical reasoning why the sqltubo hanging around? I have not seen this problem, but informix guys are suggesting to us that we should have signal handlers in all our process, doing an sqlexit() call. Is it necessary to have a Signal handler doing this? I really appreciate your help on this. Thanks in advance, Shyam --- -- ---------------------------------------------------------------------------- Shyam Davuluru |(408)246 2046 (R) Email Address: shyam@robadome.com |(408)492 4328 (W) Rolm Siemens | |