home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.informix
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!nntp.barrnet.net!nntp.pactel.com!eric
- From: eric@nit.pactel.com (Eric Pederson)
- Subject: Re: ESQL/C -- sqlturbo and sqlexit()
- Message-ID: <C1Horv.1MH@nit.pactel.com>
- Organization: Pac*Tel Corporation
- References: <FORNEY.93Jan19085549@vega.bsdsun> <1993Jan21.090631.17764@pyra.co.uk>
- Date: Wed, 27 Jan 1993 01:44:35 GMT
- Lines: 18
-
- It seems that sqlexit() in ESQL/C version 4.x is doing a blocking
- wait() instead of a waitpid() or a non-blocking wait3() or wait4().
- If I want to sqlexit() before my other children have died, then the sqlexit()
- hangs. Also, while it is hanging, I do a "ps" and find that sqlturbo is
- *still* running. Isn't it supposed to wait() *after* the kill? If (while it
- is hanging) I kill my application with a SEGV signal, I get the following in
- an "adb" traceback:
-
- _wait4(?)
- __DYNAMIC(0xefffe22c,0x0,0x2a9400,0x2,0x10,0x0) + 4
- _killbackend(0x5035,0x0,0x0,0x10,0x2b2a68,0xc) + 34
- _sqlexit(0x1,0x1f,0xefffe318,0x2c38d0,0xef7ea760,0x1) + 4
-
- Is this fixed in version 5.0 or is there a way around using sqlexit()
- to stop the sqlturbo process when you are finished with ESQL?
- --
- Eric Pederson Pac*Tel Corporation
- eric@nit.pactel.com 510-210-8890
-