Appendix B Revision History for this Manual

This section describes the revision history for this manual.

Current Version—Solaris 8 7/01 Release

The current version of this manual applies to the Solaris 8 7/01 release.

New Parameters

This section contains new parameters.

logevent_max_q_sz

This parameter is new in the Solaris 8 1/01 release. See logevent_max_q_sz for more information.

Changes to Existing Parameters From the Previous Release (Solaris 8 1/01)

These parameters were corrected.

maxusers

The following section changed.

Range

1 to 2048

to:

Range

1 to 2048, based on physical memory without any setting in the /etc/system file.

1 to 4096, if set in the /etc/system file.

segspt_minfree

The following section changed.

Range

0 to 32,767

to:

Range

0 to 50% of physical memory.

shmsys:shminfo_shmseg

The following section changed.

Description

Limit on the number of shared memory segments that any one process can create.

to:

Description

Limit on the number of shared memory segments that any one process can attach.

tmpfs:tmpfs_maxkmem

The following section changed.

Default

to:

Default

One page or 4% of physical memory, whichever is greater.

tmpfs:tmpfs_minfree

The following section changed:

Units

Bytes

to:

Units

Pages

tcp_conn_req_max_q0

The following section was changed.

When to Change

For applications, such as web servers that might receive excessive connection requests, you can increase the default value to match the incoming rate.

The following explains the relationship between tcp_conn_req_max_q0 and the maximum number of pending connections for each socket.

When a connection request is received, TCP first checks if the number (N) of pending TCP connections (three-way handshake is done) waiting to be accepted exceeds the maximum for the listener. If the connections are excessive, the request is denied. If the number of connections is allowable, then TCP checks if the number of incomplete pending TCP connections exceeds the sum of N and tcp_conn_req_max_q0. If it does not, the request is accepted. Otherwise, the oldest incomplete pending TCP request is dropped.

to:

When to Change

For applications, such as web servers that might receive excessive connection requests, you can increase the default value to match the incoming rate.

The following explains the relationship between tcp_conn_req_max_q0 and the maximum number of pending connections for each socket.

When a connection request is received, TCP first checks if the number of pending TCP connections (three-way handshake is done) waiting to be accepted exceeds the maximum (N) for the listener. If the connections are excessive, the request is denied. If the number of connections is allowable, then TCP checks if the number of incomplete pending TCP connections exceeds the sum of N and tcp_conn_req_max_q0. If it does not, the request is accepted. Otherwise, the oldest incomplete pending TCP request is dropped.

tcp_rexmit_interval_max

The following section changed.

Range

1 millisecond to 20 seconds

to:

Range

1 millisecond to 2 hours

tcp_slow_start_initial

This parameter changed.

See tcp_slow_start_initial for more information.

Changes to Existing Parameters From the Previous Release (Solaris 8)

shmsys:shminfo_shmmin

The following section changed.

When to Change

No known reason.

To:

When to Change

Not recommended. System programs such as powerd might fail if this value is too large. Programs attempting to create a section smaller than the value of shminfo_shmmin will see an EINVAL error when attempting to create the segment and generally, will exit.

See shmsys:shminfo_shmmin for more information.

semsys:seminfo_semmnu

This parameter was added because it was left out inadvertently.

See semsys:seminfo_semmnu for more information.