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

1 2 3

  /test/ontest-stc2/src/tools/tet/contrib/ctitools/src/scripts/patch_diffs/
README 11 the file for the correct configuration.
  /test/stcnv/usr/src/tools/tet/contrib/ctitools/src/scripts/patch_diffs/
README 11 the file for the correct configuration.
  /test/stcnv/usr/src/suites/storage/comstar/
README 43 would be run on one configuration. See each specific framework section for
114 5. It's assumed that the following CONFIGURATION, and EXECUTION steps in
122 CONFIGURATION:
124 Please refer to the TEST SUITE CONFIGURATION segment for each target in each
138 1. The test configuration requires both a FC Initiator and FC Target host,
144 configuration information such as target group, host group, view entry
164 TEST SUITE CONFIGURATION:
166 Test suite configuration must be done as root.
185 The configuration file will be created as a result of the arguments specified
186 in the run_test command line. Once the configuration operation has bee
    [all...]
  /test/ontest-stc2/src/suites/net/nicdrv/doc/
ReleaseNote 43 configuration can not be restored by running stf_unconfigure.
  /test/stcnv/usr/src/suites/net/nicdrv/doc/
ReleaseNote 43 configuration can not be restored by running stf_unconfigure.
  /test/ontest-stc2/src/suites/share/
README 33 file system share configuration utility.
122 TEST SUITE CONFIGURATION :
143 filesystem types on the devices given, based on the configuration type. This
155 If not already done, from the configuration phase do the following to
181 The unconfiguration of the test suite simply takes out the configuration file
  /test/stcnv/usr/src/suites/fs/share/
README 33 sharectl, they are file system share configuration utilities.
52 alternative directory by setting TESTDIR before configuration:
66 use alternative path, please set this variable before configuration:
186 TEST SUITE CONFIGURATION:
188 Test configuration is required to be done as root.
224 If not already available from the configuration phase, set the
259 - the configuration file
327 | configure | for test suite configuration only | not a test |
  /test/stcnv/usr/src/suites/nfs/nfsgen/
README 78 User needs to set SETUP env variable to specify which configuration
80 configuration files. If SETUP=nfsv4, top-level configuration files
83 Top-level configuration files also perform some common tasks required
301 CONFIGURATION
326 overrides those specified at configuration phase, you MUST NOT do that
328 since the suite has done corresponding configuration against those variables,
338 with RDMA configuration, so if you run the suite w/RDMA, those tests
370 and server. If SETUP!=none, the suite configuration will
382 environment manually and let the test suite skip configuration
    [all...]
  /test/ontest-stc2/src/suites/iSCSI/
README 113 TEST SUITE CONFIGURATION :
129 Other configurable variables that can be set in the configuration line :
143 If not already done, from the configuration phase do the following to
173 The unconfiguration of the test suite simply takes out the configuration file
  /test/ontest-stc2/src/suites/os/xvm/virt-install/
README 136 TEST SUITE CONFIGURATION / EXECUTION:
147 2. Create a configuration file to use for the suite. See
153 # run_test -F /path/to/your/configuration/file virt-install
178 file in the configuration file.
180 PXE CONFIGURATION (HVM guests ONLY):
193 configuration file and fill in the mac address.
README.CONFIG 61 The configuration template is split into 4 sections:
  /test/stcnv/usr/src/suites/storage/fwflash/
README 108 TEST SUITE CONFIGURATION
110 Test suite configuration is required to be done as root.
135 Another variable that can be set in the configuration line:
147 If not already available from the configuration phase, set the
  /test/ontest-stc2/src/tools/krb5tools/bin/
krb5nfscfg.ksh 62 configuration
138 # if -c is specified, clean up localhost with previous configuration and exit
  /test/stcnv/usr/src/tools/genutils/krb5tools/bin/
krb5nfscfg.ksh 65 configuration
146 # if -c is specified, clean up localhost with previous configuration and exit
  /test/stcnv/usr/src/tools/krb5tools/bin/
krb5nfscfg.ksh 62 configuration
137 # if -c is specified, clean up localhost with previous configuration and exit
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/domain/
README 69 daemon thread waits before it checks domain configuration changes. Its value
  /test/ontest-stc2/src/suites/nfs/sharemnt/
README 198 with following configuration:
208 with following configuration:
255 before configuration:
269 For example, set the following variables before configuration:
280 before configuration:
286 before configuration, e.g. to default and v3, do:
297 CONFIGURATION:
349 - others: tests require specific system configuration
  /test/ontest-stc2/src/suites/storage/megacli/
README 91 TEST SUITE CONFIGURATION
118 Other configurable variables that can be set in the configuration line:
130 Warning: the enable of CFGCLEAR option will destroy all configuration on
132 configuration, especially there should not have root file system located
139 If you haven't done this at configuration phase, set the environment
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/domain/
README 69 daemon thread waits before it checks domain configuration changes. Its value
  /test/stcnv/usr/src/suites/storage/iSCSI/
README 135 TEST SUITE CONFIGURATION:
137 Test suite configuration is required to be done as root.
151 Other configurable variables that can be set in the configuration line:
165 If not already available from the configuration phase, set the following
192 The unconfiguration of the test suite simply takes out the configuration
  /test/stcnv/usr/src/suites/os/xvm/virt-install/
README.CONFIG 55 The configuration template is split into 4 sections:
  /test/ontest-stc2/src/suites/iSCSI/src/utils/
remote_initiator.ksh 461 # Attempt to cleanup the entire configuration whether the
638 # the static configuration bits are correct.
805 # Source in the current configuration
851 # Just need to cleanup configuration after a reboot.
902 # Setup global configuration based on global variables as
906 # a static-config. Setup configuration for targets as
1047 reset_client_timer "iscsiadm configuration"
1161 echo "fdisk configuration failed" >> $CLIENT_LOG_FILE
1174 echo "format configuration failed" >> $CLIENT_LOG_FILE
  /test/stcnv/usr/src/suites/storage/iSCSI/src/utils/
remote_initiator.ksh 461 # Attempt to cleanup the entire configuration whether the
638 # the static configuration bits are correct.
805 # Source in the current configuration
851 # Just need to cleanup configuration after a reboot.
902 # Setup global configuration based on global variables as
906 # a static-config. Setup configuration for targets as
1047 reset_client_timer "iscsiadm configuration"
1161 echo "fdisk configuration failed" >> $CLIENT_LOG_FILE
1174 echo "format configuration failed" >> $CLIENT_LOG_FILE
  /test/ohacts/src/doc/dataservice/
README 94 Increase WAIT_TIME_FOR_DAEMON configuration variable and re-run
108 This is a global configuration variable and increases the max wait
  /test/ohacts/src/tset/dataservice/doc/
README 29 This file contains a list of configuration variables which are set in
31 configuration variable values are based on the contents of the

Completed in 1560 milliseconds

1 2 3