another Linux/SE zombie problem
Posted in 1998
Sorry for continuing on with the Linux/se/zombie issue-
We have an Online server running on NT (a live production box) and I am
testing SE on linux.
The online is remote to our office, but I can connect to it with various
utilities, including the GUI SQL editor and dbaccess, from my desktop.
On the SE/Linux box, I connect in three different ways -
1) Perl/DBI/CGI script allowing development for a web based front end.
2) telnet to the linux box and use dbaccess
3) SQL editor/dbaccess from my own workstation.
For the sqlhosts on the Linux/SE:
If I define sesoctcp as the protocol, and start the sqlexecd daemon,
(either alone or with the 'nozombie' program) - zombie processes are
created after using dbaccess on the linux box - everything else works
fine, (remote connect from my desktop, and the Perl/DBI scripts - no
zombies are created via these connects)
If I define seipcpip as the protocol, and do not start sqlexecd, then
dbaccess on the linux box and Perl/DBI both work fine - and no zombie
processes are created. However, I cannot connect from my NT box by
defining seipcpip in SETNET32.
It seems to me that using sesoctcp as a protocol is requried for
comapatability with later online utilities. Is there:
a) a way to get SETNET32 to use seipcpip to a remote machne?
b) any other solutions to getting SE/Linux to use sesoctcp without
creating zombies when exiting dbaccess, (I have reviewd and tried all
soloutions mentioned in the newsgroups)?
c) Is the seipcpip protocol meant to be used for remote connects?
Thanks for any more suggestions that can be offerd-