Accepts option-value pairs where the option is a physical test name, and its value as "Enable" or "Disable" which indicates whether the test probe must be enabled or disabled. By default, all test probes are enabled. The PROBE_SELECTION parameter can accept any number of option-value pair in the form:

PROBE_SELECTION xxxtest=Disable, yyytest=Disable,....

For example to disable vmemtest and pmemtest:

PROBE_SELECTION vmemtest=Disable,pmemtest=Disable

Specifies the maximum log size for VTS generated logs. The value is accepted in the numeric form as a positive integer. The unit is in MB. By default, the size of a log is 1MB.

For example, to set the maximum log file size to 5 MB:

MAX_LOG_SIZE 5

Logs the consolidated report sunvts.rpt at the end of a testing session. The option with a value of 1 allows the application to generate the report. By default, VTS does not generate this report unless the configuration option is set. The consolidated report is located under /var/sunvts/logs/ directory.

For example, to generate the VTS report:

VTS_REPORT_GENERATE 1

Enables the delay option, which delays forking of physical tests within a Logical Test by a specified value. The parameter accepts option-value pairs where the option is the Logical Test name and its value is the delay time in seconds. The DELAY parameter can accept any number of option-value pair in the form:

DELAY LTname1=value1, LTname2=value2,....

For example, to add a delay of 10 and 15 seconds before the start of Network and Graphics Test respectively:

DELAY Network=10, Graphics=15

Denotes the minimum amount of swap space to be reserved by the VTS harness (vtsk). The software will stop invoking new test instances when the available swap space amount falls below this specified threshold amount. Set the value to "default", XXXMB, or XX%. By default, this threshold amount is 15% of total configured swap space. If specified with % suffix, the percentage of total configured swap space is assumed. The specified amount must be between lower and upper limits of 5% and 75% of total configured swapspace respectively. If the specified amount is too less or too high, the nearest acceptable value will be assumed.

For example:

• RESERVE_SWAP_MIN default

• RESERVE_SWAP_MIN 200MB

• RESERVE_SWAP_MIN 35%

Denotes the maximum amount of swap space to be reserved. If the amount of swap available is greater than RESERVE_SWAP_MIN but less than RESERVE_SWAP_MAX, the software will delay invoking new test instances by LOW_SWAP_DELAY seconds. RESERVE_SWAP_MAX must be between 15% and 75% of the total configured swap space. By default, this value is set to 25%.

For example, to set the maximum amount of swap space reserved to 45%:

RESERVE_SWAP_MAX 45%

Specifies the time that the software waits before invoking a new test instance, when the system is low on memory. The time value is in seconds. The default value is 3 seconds.

For example, to set a delay for a new test invocation when the system is low on memory:

LOW_SWAP_DELAY 5

Takes the name of a profile that has to be specifically run for a platform. The custom platform name specified with this option should match the profile name of the VTS rules file to run the specific profile. This is useful when the testing behavior of a platform cannot be appropriately identified under the categories of a defined platform, an architechture type, or the system processor type.

For example:

VTS_CUSTOM_PLATFORMNAME Genesis

Specifies the maximum threshold that Alert messages can be accepted. Alert messages are used by the tests to communicate messages that can be fatal in nature but can be retried for a certain time to see if the condition improves and the test can start functioning smoothly. But these messages will not be ignored beyond the threshold. If the Alert messages reach the threshold, the Logical test receives an error and is stopped. The value is a count and is a positive numeric integer value. between 1 and 9999.

For example:

ALERT THRESHOLD 10

In case of a test probe hang, sets a time limit that the application will use to kill the test probes that did not complete in certain span of time. The option takes the time value in minutes.Vtsk kills the hung test probe after a default time of 15 mins.

For example:

PROBE_TIME_LIMIT 10

Enables logging the task's elapsed time information in the sunvts.info logs. This information will not be logged by default. To enable logging the task's elapsed time, set the value to 1.

For example:

TASK_TIMING_ENABLE 1

Specifies the time limit beyond which the status of the test should move from from "Stopping" to "Idle". This is useful to bring the VTS status to "Idle" when a test or group of tests takes some time to clean up the routines after receiving the stop command, and the system status waits on "Stopping". The time unit is in minutes. The minimum value allowed is 2 minutes, and any value below this time is ignored and is set to 2 minutes.

For example, to set the IDLE time limit to 10 mins, add the line as:

VTSK_IDLE_TIME_LIMIT 10

Specifies an alternate directory for writing the core files in case of any exception conditions. The absolute path name of the directory needs to be specified here. When this parameter is not specified,the software dumps the core to the directory where the packages are installed, which is the default behaviour.

For example:

CORE_DIR /export/home/corefiles

or

CORE_DIR

Enables additional logging of detailed test runtime status. To enable this set the parameter value to 1.

VTSK uses 256MB per cpu for its calculation on lower or higher end machines (if it is less than 256 MB per CPU it willtreat the system as a low configuration system). Throught the configuration file, this parameter provides a way to fine tune the value: if needed.

For example:

MEMORY_PER_CPU 128