RE: [cobalt-users] Interbase on RaQ4

["Mike Ciesiensky, Jr." <MikeC@xxxxxxxxxxxxxxxxxxxxx>]

>I telnet to our raq4,
> under admin, type in "ibmgr - start"
> Nothing: bash bad command ..

Ok, I've never used ibmgr on the Raq.  I installed UnixODBC on the Raq
(unixodbc.com).  Then I ran 'isql' to create an Interbase Database and test
connections and such.

I found out that you can't use client tools to tab directly into the
IBServer if you are using a certain version of Interbase (which is on the
RAQ).  That's why I used IBServer on my machine.  I can create databases on
my machine through a cool GUI interface and then upload them to the server.

You can use IBAccess to access your Databases on your server from your
client machine.  It has a great interface.

I had someone help me, so here is some of our dialog...

-------------------------------------
TO CHECK THAT THE IBSERVER IS STARTED

On the linux box have a look in the file /etc/services (like on NT). You
should have a

gds_db        3050/tcp  # InterBase Database Remote Protocol

And in the file /etc/inetd.conf

gds_db  stream  tcp     nowait.30000      root
/usr/local/sbin/gds_inet_server
gds_inet_server # InterBase Database Remote Server

That line says that if a connection comes in on port 3050 start up the
program
gds_inet_server in the directory /usr/local/sbin and run as root.

Now you can test that, on the linux box, by trying to connect

telnet localhost 3050

If it connects and sits there the server is listning, otherwise you may get
a error back.


QUESTION:
> The /etc/inetd.conf has this at the end of the file. I deleted a '#' in
> front of the gds_db. Does all that need to be before the '# End of
> inetd.conf'??  Do I need to restart anything for the inetd.conf to be
> re-initialized or something??

Yes, find the process id of inetd

ps -aux | grep inetd

In my case this gives

root     20376  0.0  0.0  1168  292 ?        S    Oct19   0:00 inetd
mike      7968  0.0  0.0  1364  524 pts/16   S    16:42   0:00 grep inetd

Then as root send process 20376 (inetd) a SIGHUP (-1) signal, this wont kill
it
but will cause it to reload

kill -HUP 20376

Now try the telnet again.
-------------------------------------

See how that goes and let me know.
Hope it helps,
Mike.