Why is inetd terminating the ODBC-ODBC Bridge server service?

inetd counts the number of server instances created in a 60 second interval. If your Easysoft ODBC-ODBC Bridge server is busy accepting a lot of connections in a short period of time, inetd may decide the server is being flooded or looping and suspend the service for a while. A typical inetd message output in this situation is:

/var/log/messages:Feb 16 14:35:41 machine inetd[52]: esoobserver/tcp
failing (looping or being flooded), service terminated for 10 min

By default, most inetd servers class 40 instances in 60 seconds as being too many. If you need a higher threshold than this, edit your inetd.conf file and edit the ODBC-ODBC Bridge server line to set a maximum number of server instances (refer to the inetd.conf(8) man page). Usually, you need to place a . and a number after the nowait to do this. For example:

esoobserver stream tcp nowait.60 root /bin/sh /bin/sh
/usr/local/easysoft/oob/server/server

Don't forget to tell inetd to reread its configuration files after making changes to inetd.conf.