Mimer SQL Documentation TOC PREV NEXT INDEX

Mimer SQL Developer Site


Networking Setup


inetd setup

The Unix command inetd is the Internet services daemon, the server process for the Internet standard services. It is usually started up at system boot time. The configuration file /etc/inetd.conf lists the services that inetd should handle. An excerpt from the file shows the syntax used in the file:

 #
 # Syntax for socket-based Internet services:
 #  <service_name> <socket_type> <proto> <flags> <user> <server_pathname> 
<args>
 #
 

When dbinstall is executed, and the inetd.conf file is found, the following line is added to the configuration file:

 mimer stream tcp nowait root /usr/bin/mimtcp mimtcp -l
 

This indicates that mimtcp should be started for the mimer service. The -l option is used standalone which implies that the default logfile should be used.

When the inetd configuration is changed, for example if mimer is added like described above, the inetd daemon must reread it. This is triggered by sending the HUP signal to the inetd process (located using the ps -ef command):

 # ps -ef | grep inetd
 root      8796     1  0  2006 ?        00:00:12 inetd
 # kill -HUP 8796
 #

xinetd setup

The Unix command xinetd stands for "the extended Internet services daemon". It is the successor to inetd and works in a slightly different way. Instead of having tasks started at system initialization time, and be dormant until a connection request arrives, xinetd is the only daemon process started and it listens on all service ports for the services listed in its configuration file. When a request comes in, xinetd starts the appropriate server.

The default xinetd definitions for Mimer SQL can be found in the file mimersql.xinetd in the installation directory called misc:

 $ cat /opt/MimerSQL-9.3.7A/misc/mimersql.xinetd
 # default: on
 # description: The MIMER service allows remote users to access the
 #              Mimer SQL database servers on this node.
 service mimer
 {
         port            = 1360
         socket_type     = stream
         wait            = no
         user            = root
         server          = /usr/bin/mimtcp
         server_args     = -l
         log_on_failure  += USERID
         disable         = no
         protocol        = tcp
 }
 $
 

If the /etc/xinetd.d directory is found when dbinstall is executed, the mimersql.xinetd file is copied there and is given the name mimer.

If the /etc/xinetd.d is not found, but /etc/xinetd.conf is found, the mimersql.xinetd contents is added at the end of the /etc/xinetd.conf file.

When the xinetd configuration is changed, for example if mimer is added like described above, the xinetd daemon must reread it. This is triggered by sending the HUP signal to the xinetd process (located using the ps -ef command):

 # ps -ef | grep xinetd
 root      8796     1  0  2006 ?        00:00:12 xinetd
 # kill -HUP 8796

Mimer
Mimer Information Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
info@mimer.se
Mimer SQL Documentation TOC PREV NEXT INDEX