Re: Newbie question: Informix SE on Linux

Hi! Nils Myklebust wrote: > On Thu, 30 Jul 1998 13:13:20 +0200, KakukZ <kakukz@meh.hu> wrote: > > >Hi! > > > >Nils Myklebust wrote: > > > >> On Wed, 29 Jul 1998 09:00:48 +0200, KakukZ <kakukz@meh.hu> wrote: > >> > >> >"localhost" is just fine in sqlhosts but Linux does not support unnamed pipes > >> >so change > >> >the sqlhosts file 2nd coloumn from "seipcipc" to "sesoctcp". > >> > >> We run it with seipcpip just fine. > > > >Can you tell me how? I'm interested. > > I run on Caldera OpenLinux Standard ver. 1.2 (kernel 2.0.33) right > now. I just installed this and SE and left the seipcpip in there and > it worked. (It's not seipcipc as you have written above though.) Yes, you are right. It's seipcpip. Sorry :) > > > >> > Also make sure > >> >that in the 4th coloumn you replace "sqlexec" to "demo_service" (or whatever > >> >you want to name it) and add this entry to "/etc/services" with port 1536. > >> >Then start sqlexecd with "$INFORMIXDIR/lib/sqlexecd demo_se". > >> > >> The services name can be anything, including sqlexec, as long as you > >> use the same name in the /etc/services file. > > > >Look at the brackets. They say "(or whatever you want to name it!!!)". I didn't > >say that it must be demo_se, BUT using sqlexec is a little bit confusing, because > >it is reserved for seipcipc. > Reserved for seipcpip I assume you mean. I didn't know there where > something called seipcipc. > > Yes you are right. I didn't think about that or even know it. > > For others: If you specify seipcpip (to use unnamed pipes for > communication between your Linux application and the database server) > the 4th entry on that sqlhosts-line is the name of the executable > database engine found in $INFORMIXDIR/lib. This is allways sqlexec for > the SE engine. If you are using the Dynamic Server (not yet on Linux) > that entry isn't used at all as far as I know if you use a non tcp/ip > based protocol (shared memory in the case of IDS). > > Now it does work using the sqlexec name even if you change to a tcp/ip > based communication, but KakukZ is of course right that it might lead > to a little confusion. > For purely local use I find it much easier to use unnamed pipes > (seipcpip) as there is no need to start any server program then. I'm on kernel 2.0.27, and I can't connect with seipcpip. That's why I assumed that unnamed pipes only supported in 2.0.30 & above. I always get a 25591 error from dbaccess. But I will NEVER give up! :) Anyone has an idea? > > > Nils Myklebust > NM Data AS > Norway > E-mail: Nils.Myklebust@nmdata.com > FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html > (Now with ODBC info under "Third party products".) Regards, KakukZ ----------------------------------------------------------------- Zoltan Kakuk kakukz@freemail.c3.hu System Administrator Mosonyi str. 9. Hungarian National Police HQ 1087, Budapest Criminal Identification Service HUNGARY -----------------------------------------------------------------