HomeSort by relevance Sort by last modified time
    Searched refs:variables (Results 1 - 25 of 48) sorted by null

1 2

  /test/ontest-stc2/src/tools/checkenv/lib/
ce_config_vars.ksh 10 # Check that a set of variables has the values set
32 # This function checks if the variables are configured as required.
72 check that a set of variables has the values set
  /test/stcnv/usr/src/tools/checkenv/lib/
ce_config_vars.ksh 10 # Check that a set of variables has the values set
32 # This function checks if the variables are configured as required.
72 check that a set of variables has the values set
  /test/ohacts/src/tset/dataservice/doc/
README 29 This file contains a list of configuration variables which are set in
44 Ex : If NUM_RGS is 2, there will be 2 variables, RG_1_NAME and RG_2_NAME
52 If NUM_RGS is 2, there will be 2 variables. RG_1_NODELIST and
59 Ex : If NUM_RGS is 2, there will be 2 variables. RG_1_NUM_PROPERTIES
85 variables.
98 variables.
126 there would be 2 variables.
147 there would be 2 variables.
185 Ex : If RG_1_R_1_NUM_DAEMONS is 2, there will be 2 variables.
199 Ex : If RG_1_R_1_NUM_FM_DAEMONS is 2, there will be 2 variables
    [all...]
  /test/ontest-stc2/src/suites/storage/megacli/
README 94 1. Set the following environment variables
118 Other configurable variables that can be set in the configuration line:
140 variables as following:
186 2. Set the environment variables
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/server/
README 37 directory based on variables in v4test.cfg file, which
  /test/stcnv/usr/src/suites/nfs/nfsv4/server/
README 37 directory based on variables in v4test.cfg file, which
  /test/stcnv/usr/src/suites/storage/megacli/
README 103 1. Set the following environment variables
127 Other configurable variables that can be set in the configuration line:
150 variables as following:
199 2. Set the environment variables
  /test/ontest-stc2/src/suites/nfs/sharemnt/
README 120 2. MUST define environment variables "SERVER"
134 5. You can define the following optional variables, if not set,
205 with the variables "NUM_GROUPS" and "NUM_ENTRYS". Eg.
228 Krb5 tests also uses three other env variables: DNS_DOMAIN,
269 For example, set the following variables before configuration:
290 Both variables must be set BEFORE or at "stf_configure" to generate
299 You can choose one of the following ways to define the variables
302 1) define environment variables
319 variables which will override those specified at configure
  /test/ontest-stc2/src/suites/nfs/fnfs/
README 115 2. Define following environment variables:
118 The following variables are optional, if not set, the default
151 You can choose one of the following ways to define the variables and
154 1) define environment variables
169 '-c' option specifying other optional variables which will override those
  /test/ontest-stc2/src/suites/zfs/
README 176 scripts location directory on the remote host. The descriptions of variables
213 o In addition, all variables to stf_configure can be set through setting
214 environment variables or defining in a file. For example:
215 In Korn Shell, you can export all variables as environment variables:
225 or, you can define all variables in a file and then via "-f" option of
  /test/ontest-stc2/src/tools/runwattr/
README 34 privileges, and zone. In addition, environment variables can
76 The -i and -e options manipulate environment variables.
77 By default, the current environment variables will be
79 -i will clear all variables from the current environment.
80 -e can be used to add or change additional variables.
365 The following three examples show how environment variables
369 1) Propagating environment variables between zones
380 2) Using -e to set extra environment variables:
393 even those variables set automatically with zlogin(1).
394 "wc -l" is used to count the number of variables define
    [all...]
  /test/stcnv/usr/src/suites/fs/zfs/
README 190 descriptions of variables are as follows:
231 o In addition, all variables to stf_configure can be set through
232 setting environment variables or defining in a file. For example:
233 In Korn Shell, you can export all variables as environment variables:
243 or, you can define all variables in a file and then via "-f" option of
  /test/stcnv/usr/src/suites/nfs/fnfs/
README 113 2. Define following environment variables:
116 The following variables are optional, if not set, the default
149 You can choose one of the following ways to define the variables and
152 1) define environment variables
167 '-c' option specifying other optional variables which will override those
  /test/stcnv/usr/src/tools/runwattr/
README 34 privileges, and zone. In addition, environment variables can
76 The -i and -e options manipulate environment variables.
77 By default, the current environment variables will be
79 -i will clear all variables from the current environment.
80 -e can be used to add or change additional variables.
364 The following three examples show how environment variables
368 1) Propagating environment variables between zones
379 2) Using -e to set extra environment variables:
392 even those variables set automatically with zlogin(1).
393 "wc -l" is used to count the number of variables define
    [all...]
  /test/ontest-stc2/src/suites/iSCSI/
README 118 1. Set the following environment variables
129 Other configurable variables that can be set in the configuration line :
144 set the environment variables :
  /test/stcnv/usr/src/suites/storage/fwflash/
README 114 Set the following environment variables:
121 Set the following environment variables:
148 required environment variables:
  /test/stcnv/usr/src/suites/net/driver-wifi/
README 162 Except UPERF, another five variables must be defined to run this test suite.
164 So for the above picture, please define the configure variables like this:
169 Some other variables are configurable also. Here is some examples that
206 Set up the environment variables:
  /test/stcnv/usr/src/suites/net/nc/
README 172 - to build the tests, set CTI-TET variables and run 'make':
223 8.2 Internal variables
228 or need to change port used for testing there is a list of variables
309 Also note that tet_startup,tet_cleanup variables are set to common_startup
312 10.2 Internal variables
315 start_nc() sets two internal variables which accessible from test purposes:
328 finish_test() can be passed the variables.
  /test/ontest-stc2/src/suites/os/xvm/virt-install/
README 74 - Set environment variables
140 1. Set the following environment variables:
  /test/ontest-stc2/src/suites/security/kmf/
README 114 all the environment variables described in the NOTES section below.
115 These environment variables may be set in any one of the methods
130 Overrideable configuration variables provided in the stf_configure phase
255 set the following variables and re-run stf_configure:
269 These variables may also be set during the stf_execute step using the
  /test/ontest-stc2/src/suites/share/
README 127 1. Set the following environment variables
156 set the environment variables :
  /test/ontest-stc2/src/suites/storage/sdts/
README 87 1. Set the following environment variables
123 set the environmental variables:
  /test/ontest-stc2/src/tools/tet/contrib/ctitools/
README 153 cti_deleteall() functions that use shared variables
234 configuration variables, e.g.:
267 inside the kernel to get configuration variables specified in tetexec.cfg,
  /test/stcnv/usr/src/tools/tet/contrib/ctitools/
README 159 cti_deleteall() functions that use shared variables
248 configuration variables, e.g.:
281 inside the kernel to get configuration variables specified in tetexec.cfg,
  /test/stcnv/usr/src/suites/storage/comstar/
README 168 1. Set up the following environment variables
190 Other configurable variables that can be set in the configuration line :
278 1. Set up the following environment variables
301 Other configurable variables that can be set in the configuration line :
412 1. Set up the following environment variables
440 Other configurable variables that can be set in the configuration line:
540 1. Set up the following environment variables
561 Other configurable variables that can be set in the configuration line :

Completed in 5279 milliseconds

1 2