SUMMARY: /dev/tcp parameters

From: Dave Acosta (
Date: Wed Dec 03 1997 - 13:53:00 CST

On Wed, Dec 03, 1997 at 11:46:34AM -0500, Dave Acosta wrote:
> Hi All.
> I have multiple Solaris 2.5.1 Ultra-1 machines with different
> /dev/tcp configuration parameters. For example one machine has
> tcp_conn_req_max and the other has tcp_conn_req_max_q and q0.
> Both machines have kernel patch 103640-12.

ANSWER: Jeff Wasilko <>
It's a side effect of patch 103582-12. It's what creates the
tcp_conn_req_max_q and tcp_conn_req_max_q0.


Attached is bug id 4063521.

Thanks, Dave
# David Acosta || Harris Corporation #
# || Corporate Information Management #
# Ph# (407) 724-3903 || 1025 W. Nasa Blvd. MS-71 #
# Fax (407) 724-3888 || Melbourne, FL 32919 #

 Bug Id: 4063521
 Category: kernel
 Subcategory: tcp-ip
 State: closed
 Synopsis: Installation of the 103582-12 patch makes ndd on tcp_conn_req_max to
Following the installation of the 103582-12 patch, one of our customer
reported warnings at boot from the inetinit script :

                "inetinit: name is non existant for this module"

He also reported some performance problems on his web server.

Just after the patch installation, the tcp_conn_req_max module doesn't
exist any more and seems to be replaced by tcp_conn_req_max_q and

Before the patch installation :
# ndd -get /dev/tcp \?
? (read only)
tcp_close_wait_interval (read and write)
tcp_conn_req_max (read and write) <--
tcp_conn_grace_period (read and write)
tcp_cwnd_max (read and write)
tcp_debug (read and write)

And after the patch installation :
# ndd -get /dev/tcp \?
? (read only)
tcp_close_wait_interval (read and write)
tcp_conn_req_max_q (read and write) <--
tcp_conn_req_max_q0 (read and write) <--
tcp_conn_grace_period (read and write)
tcp_cwnd_max (read and write)
tcp_debug (read and write)

In his /etc/init.d/inetinit (/etc/rc2.d/S69inet), the customer was
setting this module :

                ndd -set /dev/tcp tcp_conn_req_max 8192

and of course, we got a warning since the first reboot following
this patch installation...

Then we tried to increase values of tcp_conn_req_max_q and tcp_conn_req_max_q0,
but with no result (surprising, no ?) !

The only workaround we found was to backout the 103582-12 and reboot but
this is only a temporary fix and is not acceptable for the future.

Perhaps the old variable name(tcp_conn_req_max) will not exist any longer
but in that case I think we should document this in the ReadMe of the patch.

On another hand I thought these two new modules should not be available before
Solaris 2.6 ? In that case it looks like a bug in the patch, no ?

Please we need to quicky provide our customer (an important mission critical
customer) with either an explanation or a new version of the patch.

Thank you in advance.

 Work around:
Simply backout the patch as the setting of tcp_conn_req_max_q and
tcp_conn_req_max_q0 doesn't seem to work as we expect it to do.
        Integrated in releases:
 Duplicate of:
 Patch id:
 See also:
SunSoft does not document private interfaces such as ndd tunables.
Customers who make use of such interfaces assume all the risks and
responsibilities of such actions.

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:10 CDT