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

1 2

  /test/ohacts/src/tset/dataservice/sample/get_dsinfo_output/
README 42 properties of both the resources in this resource group and also names
51 described above, this file also includes client program information
56 timeout value for the client program and also the machine on which
69 groups, Resource properties and also names of the application and
78 described above, this file also includes client program information
83 timeout value for the client program and also the machine on which to
  /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/
README 38 There are also ksh script testing the nfsmapid domain and NFSv4 providers.
  /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/
README 38 There are also ksh script testing the nfsmapid domain and NFSv4 providers.
  /test/ontest-stc2/src/suites/iSCSI/
README 33 suite will also confirm the target creation and configurations,
70 It is also acceptable to use an nfs accessible version of the SUNWstc-tetlite
95 It is also acceptable to use an nfs accessible version of the SUNWstc-iSCSI
99 The test suite source can also be installed locally, built in the source
  /test/ontest-stc2/src/suites/share/
README 63 It is also acceptable to use an nfs accessible version of the SUNWstc-tetlite
87 It is also acceptable to use an nfs accessible version of the SUNWstc-share
90 The test suite source can also be installed locally, built in the source
104 The build can also install into a proto directory below the defined CODEMGR_WS
  /test/ontest-stc2/src/tools/checkenv/lib/
ce_zones_active.ksh 33 # Check to see if zones are active on the system. This will also call
140 also calls ce_zones to verify that the system supports zones.
  /test/stcnv/usr/src/tools/checkenv/lib/
ce_zones_active.ksh 33 # Check to see if zones are active on the system. This will also call
140 also calls ce_zones to verify that the system supports zones.
  /test/stcnv/usr/src/suites/os/xvm/virt-install/
README 96 The build can also install into a proto directory below the workspace
97 root directory. The workspace root (also referred to here as WS_ROOT)
README.CONFIG 40 This network name/IP also needs a valid mac address. In order to
  /test/stcnv/usr/src/suites/net/driver-wifi/
README 96 It is also acceptable to use an nfs accessible version of SUNWstc-tetlite.
119 It is also acceptable to use an nfs accessible version of SUNWstc-driver-wifi.
131 The build can also install into a proto directory below the workspace
169 Some other variables are configurable also. Here is some examples that
194 IBSS_TP{5,6}_SESSIONS also.
  /test/ontest-stc2/src/tools/tet/contrib/ctitools/
README 77 environment variable is set, the built code will also be copied to
121 can also remove the package with -R suitename.
223 They must also be linked with the archive library likmodapi.a (as opposed to
233 in tetexec.cfg. You must also specify the TET_SU_TOOL and TET_KMOD_TOOL
270 same scenario processing facility also applies to kernel tests. For example,
  /test/stcnv/usr/src/tools/tet/contrib/ctitools/
README 83 environment variable is set, the built code will also be copied to
127 can also remove the package with -R suitename.
237 They must also be linked with the archive library likmodapi.a (as opposed to
247 in tetexec.cfg. You must also specify the TET_SU_TOOL and TET_KMOD_TOOL
284 same scenario processing facility also applies to kernel tests. For example,
  /test/stcnv/usr/src/suites/storage/iSCSI/
README 33 will also confirm the target creation and configurations, use the
74 It is also acceptable to use an NFS-accessible version of the
98 It is also acceptable to use an NFS-accessible installation of the
117 The build can also install into a 'proto' directory below the workspace
  /test/stcnv/usr/src/suites/fs/share/
README 73 or define SHR_TMPDIR in run_test command line directly, and you can also
120 It is also acceptable to use an NFS-accessible version of the
149 It is also acceptable to use an NFS-accessible version of the
168 The build can also install into a 'proto' directory below the workspace
213 on the fs type of TESTDIR. This also means that any data in the TESTDIR
  /test/ontest-stc2/src/suites/net/nicdrv/
README 86 You can also use console for this purpose.
140 they can also ping the hostname of each other.
  /test/ontest-stc2/src/suites/os/xvm/virt-install/
README 105 The test suite source can also be installed locally, built in the source
119 The build can also install into a proto directory below the defined CODEMGR_WS
  /test/ontest-stc2/src/suites/net/nicdrv/tools/nfscorrupt/
README 47 by 0x01 for each file wrote. The file size also starts out at a random
  /test/stcnv/usr/src/suites/net/nicdrv/tools/nfscorrupt/
README 47 by 0x01 for each file wrote. The file size also starts out at a random
  /test/stcnv/usr/src/suites/nfs/nfsv4/
README 47 package for execution. Scripts are also included for automation of setup
130 If SERVER is zfs boot, and you also want to run the tests over UFS,
134 Similarly, if SERVER is ufs boot, and you also want to run the tests over ZFS,
195 The following variable must also be defined:
252 You can also build the package from the top suite level, after the "proto"
279 You may also run tests in a loop after system setup; but the 'recovery' subdir
301 You may also use the <subdir>.flist (test file list) under each subdir to
  /test/stcnv/usr/src/suites/nfs/loadstress/
README 71 It is also acceptable to use an nfs accessible version of the
  /test/ontest-stc2/src/suites/nfs/fnfs/
README 58 o It is also acceptable to use an nfs accessible version of the
233 - Tests may also fail if the network between the local system and SERVER
  /test/ontest-stc2/src/suites/nfs/sharemnt/
README 60 o It is also acceptable to use an nfs accessible version of the
116 Also, please do the followings before running the tests:
228 Krb5 tests also uses three other env variables: DNS_DOMAIN,
  /test/stcnv/usr/src/suites/net/nicdrv/
README 91 control. You can also use the system console for this purpose.
147 other by root, and they should also be able to ping each other
  /test/stcnv/usr/src/suites/nfs/fnfs/
README 58 o It is also acceptable to use an nfs accessible version of the
232 - Tests may also fail if the network between the local system and SERVER
  /test/stcnv/usr/src/suites/nfs/loadstress/tests/workloads_in_zones/
README 156 and unmounting file systems, also the server ZFS filesystems.
237 subdirs. These threads also emulate writing log file behavior.

Completed in 5370 milliseconds

1 2