G.2 List of Kernel Parameters (in Solaris)
Note the following.
-
For non-global zones, set the /etc/project file in each non-global zone as a parameter set using a /etc/project file. For a shared IP zone, set the /etc/system file in a global zone as the parameter set using a /etc/system file. For an exclusive IP zone, set the /etc/system file in the exclusive IP zone.
-
For the daemon processes that start during system boot, the values set in the system project in /etc/project is not validated until executing the following commands. If you are using parameters set in the system project, validate them by editing the startup script(/etc/opt/jp1base/jbs_start) as follows. Add these lines on to the next line where "unset CLASSPATH" is set.
newtask -p system /usr/bin/true #1 newtask -p system -c $$ #2
#1: For execution of this command, add the line only in the first script in the startup sequence because the one time execution of the command set all the processes executing from system project. You do not need to add it in multiple scripts.
#2: For execution of this command, add the line in all scripts that starts intended daemon processes because the execution of the command sets only for a process.
- Organization of this subsection
(1) Adjusting the Default System Resource Settings
The table below shows the estimated values for the default system resource settings that need to be adjusted to run JP1/Base.
(a) Parameters to be added
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Process |
maxuprc max_nprocs |
|
|
||
|
#: If using the JP1/SES compatibility function, estimate the value for this parameter as indicated in Appendix G.2(4) When using the JP1/SES compatibility function.
If you are using a logical host, for the max_nprocs parameters, base your estimate on the number of commands executed concurrently on the computer as a whole (logical host and physical host).
(b) Parameters to be adjusted
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
File system |
process.max-file-descriptor |
Number of hosts managed by the local host in a system using JP1/IM - Manager# + 60 |
#: Required only when using JP1/IM - Manager.
If you are using a logical host, for the process.max-file-descriptor parameter, base your estimate on whichever host (logical host or physical host) manages the largest number of hosts.
(2) When using the command execution function
The tables below show the estimated values for the kernel parameters that need to be adjusted to run JP1/Base when using remote commands and automated actions issued from JP1/IM - Manager.
(a) Parameters to be added
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Process |
maxuprc max_nprocs |
(Number of concurrently executable remote commands + Number of concurrently executable automated actions#1) × 3#2 + Number of Execute Command windows#3, #4 |
|
Shared memory |
project.max-shm-ids |
1 + (Number of concurrently executable remote commands + Number of concurrently executable automated actions#1)#6 |
|
Semaphore |
project.max-sem-ids |
3 |
- #1:
-
The default is 1. The estimate can be increased to a maximum of 48 by adjusting the value in the jcocmddef command.
- #2:
-
Three processes are generated by each remote command or automated action. Take these processes into account when estimating the number of remote commands and automated actions. When processing finishes, the process disappears. Multiple processes may
be generated if two or more commands are executed in succession. Estimate this value for the host specified as the command execution host.
- #3:
-
The number of Execute Command windows opened by the connected JP1/IM - View. The number of processes increases according to the number of open windows. When an Execute Command window closes, the corresponding process disappears. Estimate this value for the manager hosts issuing commands.
- #4:
-
The number of Execute Command windows in JP1/IM - Manager is a maximum of 64.
- #5:
-
If the total estimate exceeds 256, assume 256 in the calculations. Estimate this value for the host on which commands are executed.
(b) Parameters to be adjusted
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Shared memory |
project.max-shm-memory |
143,468 or greater |
(3) When using the health check function
The tables below show the estimated values for the system resource settings that need to be adjusted to run JP1/Base when using the JP1/Base health check function.
(a) Parameters to be added
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Shared memory |
project.max-shm-ids |
10 + 10 × Number of logical hosts |
(b) Parameters to be adjusted
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Shared memory |
project.max-shm-memory |
215,644 or greater |
(4) When using the JP1/SES compatibility function
The tables below show the estimated values for the system resource settings that need to be adjusted to run JP1/Base when using the JP1/SES compatibility function.
Even if the JP1/SES compatibility functionality is not consciously used, you need to perform the necessary calculations using these estimations if the v5-unused flag is not set for the options parameter in the event server setting file (conf).
- Note:
-
If an overwrite installation is performed from JP1/Base version 7 or earlier, the v5-unused flag is not set.
(a) Parameters to be added
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Process |
maxuprc max_nprocs |
|
|
Shared memory |
project.max-shm-ids |
1 |
|
Semaphore |
project.max-sem-ids |
10 |
|
Message queue |
project.max-msg-ids |
2 |
|
process.max-msg-messages |
2 |
(b) Parameters to be adjusted
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Shared memory |
project.max-shm-memory |
64 or greater |
(5) When a local action function is used
The estimated value of system resources that must be adjusted as JP1/Base when a local action function is used is shown below.
(a) Parameters to be added
|
System resource |
Parameter |
Estimate |
|---|---|---|
|
Process |
maxuprc max_nprocs |
Number of concurrently executable local actions |