Easysoft ODBC-ODBC Bridge

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

Last Reviewed:
12th January 2024/dd>

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 ODBC-ODBC Bridge Server is being flooded or looping and suspend the service for a while. A typical message output by inetd looks like this:

/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 count 40 instances in 60 seconds as too many. If you need a higher threshold than this, you need to edit your inetd.conf file and amend the ODBC-ODBC Bridge Server line to set a maximum number of server instances [see the inetd.conf(8) man page]. Usually, all that is involved is placing a . and a number after the nowait.


esoobserver stream tcp nowait.60 root /bin/sh /bin/sh

Do not forget to tell inetd to reread its configuration files after making changes to inetd.conf.

Applies To

Knowledge Base Feedback

* Did this content help you?
* Please select one option based on your first choice:

(* Required Fields)