Pseudo Terminals
pt_cnt (Pre-Solaris 7 and the Solaris 7 Release)
| Description | Number of /dev/pts (the pseudo terminal devices used by telnet
or rlogin for network logins) entries to create on a reconfiguration
boot. This parameter effectively limits the number of users that can simultaneously
be logged in across the net to the value of pt_cnt. You
must do a reconfiguration boot (boot -r) after making the
change to the /etc/system file for the additional device
nodes to be created.
| | Data Type | Signed integer
| | Default | 48
| | Range | 0 to maxpid
| | Units | logins/windows
| | Dynamic? | No
| | Validation | None. Excessively
large values hang the system.
| | When to Change | When the
desired number of users cannot log in to the system.
| | Commitment Level | Unstable
|
Sun4u Specific
enable_grp_ism (Solaris 2.6 Release)
| Description | Enables a shared memory
Translation Setaside Buffer (TSB) capability for System V Shared Memory that
has been attached with the SHARE_MMU flag set. This parameter
is available in, at minimum, patch 105181-05 for the Solaris 2.6 release.
Starting with the Solaris 7 release, the parameter name has been removed,
but the system implements this parameter by default.
| | Data Type | Signed integer
| | Default | 0
| | Range | 0 (disabled) or 1 (enabled)
| | Dynamic? | No
| | Validation | None
| | When to Change | Turn on when using
System V Shared Memory attached with the SHARE_MMU flag
set.
| | Commitment Level | Unstable
|
System V Shared Memory
shmsys:shminfo_shmmax (Solaris 9 12/02)
| Description | Maximum size of system
V shared memory segment that can be created. This parameter is an upper limit
that is checked before the system sees if it actually has the physical resources
to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose
size is larger than the specified value will fail with an EINVAL error.
| | Data Type | Unsigned long
| | Default | 8,388,608
| | Range | 0 - MAXINT on 32-bit systems,
MAXINT64 on 64-bit systems
| | Units | Bytes
| | Dynamic? | No. Loaded into shmmax field of shminfo structure.
| | Validation | None
| | When to Change | When the default
value is too low. Generally changed at the recommendation of software vendors,
but unless the size of a shared memory segment needs to be constrained, setting
this parameter to the maximum possible value has no side effects.
| | Commitment Level | Unstable
|
Network Cache and Accelerator (NCA) Tunable Parameters
sq_max_size (Solaris 9 12/02 Release)
| Description | The depth of the syncq
(number of messages) before a destination streams queue generates a QFULL message.
| | Default | 2 messages
| | Range | 1 to 0 (unlimited)
| | Dynamic? | No
| | When to Change | When NCA is running
on a system with a lot of memory, increase this parameter to allow drivers
to queue more packets of data. If a server is under heavy load, increase this
parameter so modules and drivers may process more data without dropping
packets or getting backlogged.
| | Commitment Level | Unstable
|
Parameters With No Functionality
The following section describes parameters whose functionality has been
removed, but the parameter might still be available for compatibility reasons.
These parameters are ignored if they are set.
Paging-Related Tunables
tune_t_gpgslo
| Description | Obsolete. Variable left
in place for compatibility reasons.
|
tune_t_minasmem
| Description | Obsolete. Variable left
in place for compatibility reasons.
|
System V Message Parameters
msgsys:msginfo_msgssz
| Description | Specifies size of chunks
system uses to manage space for message buffers. Obsolete since the Solaris
8 release.
| | Data Type | Signed integer
| | Default | 40
| | Range | 0 to MAXINT
| | Dynamic? | No. Loaded into msgtql field of msginfostructure.
| | Validation | The space consumed by
the maximum number of data structures that would be created to support the
messages and queues is compared to 25% of the available kernel memory at the
time the module is loaded. If the number is too big, the message queue module
refuses to load and the facility is unavailable. This computation does include
the space that might be consumed by the messages. This situation occurs only
when the module is first loaded.
| | When to Change | When the default
value is not enough. Generally changed at the recommendation of software vendors.
| | Commitment Level | Obsolete
|
|
Previous