| /test/ontest-stc2/src/suites/net/nicdrv/tools/nfscorrupt/ |
| README | 41 a instance of the testcorrupt binary is started on each mount. The
42 testcorrupt binary writes files across the nfs mount and calculates
46 binary uses patterns from 0x00 to 0xff and increments the pattern
|
| /test/stcnv/usr/src/suites/net/nicdrv/tools/nfscorrupt/ |
| README | 41 a instance of the testcorrupt binary is started on each mount. The
42 testcorrupt binary writes files across the nfs mount and calculates
46 binary uses patterns from 0x00 to 0xff and increments the pattern
|
| /test/stcnv/usr/src/tools/diskomizer/ |
| Makefile | 37 binary: install
|
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/domain/ |
| README | 81 The reason is we do that by using mdb to modify nfsmapid(1M) binary file.
|
| /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/domain/ |
| README | 81 The reason is we do that by using mdb to modify nfsmapid(1M) binary file.
|
| /test/ontest-stc2/src/suites/storage/sdts/ |
| README | 40 3. To test SMP expander function, you need to download the binary of "lsiutil"
42 you can ignore the section to install lsiutil binary.
50 LSIUTIL BINARY INSTALLATION
52 To run SMP test cases, you must copy lsiutil binary to testing platform.
62 binary, following is an example of x86 platform.
|
| /test/ontest-stc2/src/tools/tet/contrib/ctitools/ |
| README | 28 bin - compiled binary and shell standalone executable utilities.
314 issue and/or remove the installed binary from the package installation.
|
| /test/stcnv/usr/src/tools/ndmpcopy/ |
| README | 70 ndmpcopy binary is created in ndmpcopy/bin directory.
133 Following this, ndmpcopy binary packages can be constructed using the
|
| /test/stcnv/usr/src/tools/tet/contrib/ctitools/ |
| README | 34 bin - compiled binary and shell standalone executable utilities.
328 issue and/or remove the installed binary from the package installation.
|
| /test/stcnv/usr/src/suites/storage/sdts/ |
| README | 45 3. To test SMP expander function, you must download the "lsiutil" binary
47 function, you can ignore installation of the 'lsiutil' binary.
59 LSIUTIL BINARY INSTALLATION
61 To run the SMP test cases, you must copy the 'lsiutil' binary to the
72 binary:
134 In addition, test suite binary packages can be constructed using the
|
| /test/ontest-stc2/src/tools/runwattr/ |
| README | 178 root binary on the system. This can then be used by any
182 1) Remove the setuid bit from the forcepriv helper binary.
231 forcepriv binary would be /some_path_name/lib/forcepriv.
289 - Installing forcepriv as a setuid/setgid 0 binary.
421 This tool is implemented as a Perl script, with a helper binary
|
| /test/stcnv/usr/src/tools/runwattr/ |
| README | 177 root binary on the system. This can then be used by any
181 1) Remove the setuid bit from the forcepriv helper binary.
230 forcepriv binary would be /some_path_name/lib/forcepriv.
288 - Installing forcepriv as a setuid/setgid 0 binary.
420 This tool is implemented as a Perl script, with a helper binary
|
| /test/ontest-stc2/src/suites/net/nicdrv/ |
| README | 157 You can run the nicdrv test suite either from a binary package or the
182 * Copy all binary code in <SUITE_ROOT>/tools directory from client to
184 or export the client binary code and make a link on server.
|
| /test/ontest-stc2/src/suites/os/xvm/virt-install/ |
| README | 80 export CC=<path to SunStudio cc binary>
|
| /test/stcnv/usr/src/suites/storage/fwflash/ |
| README | 98 In addition, test suite binary packages can be constructed using the
|
| /test/ontest-stc2/src/suites/iSCSI/src/utils/ |
| remote_initiator.ksh | 544 echo "does not contain the expect binary." >> \
|
| /test/stcnv/usr/src/suites/storage/iSCSI/src/utils/ |
| remote_initiator.ksh | 544 echo "does not contain the expect binary." >> \
|
| /test/stcnv/usr/src/suites/net/nicdrv/ |
| README | 180 You can run the nicdrv test suite either from a binary package or the
|
| /test/stcnv/usr/src/suites/storage/iSCSI/ |
| README | 125 In addition, test suite binary packages can be constructed using the
|
| /test/ontest-stc2/src/suites/iSCSI/src/lib/ksh/ |
| utils_common.ksh | 37 # Define the scale binary that is used to do proper scaling, based
467 # - Verify that the iscsitadm binary exists
[all...] |
| /test/stcnv/usr/src/suites/storage/iSCSI/src/lib/ksh/ |
| utils_common.ksh | 37 # Define the scale binary that is used to do proper scaling, based
467 # - Verify that the iscsitadm binary exists
[all...] |
| /test/ontest-stc2/src/suites/os/smf/tests/svccfg/doc/ |
| ASSERTIONS | 108 binary file, non-existent file, directory, device.
927 binary file, non-existent file, directory, device.
1144 binary file, non-existent file, directory, device.
[all...] |
| /test/stcnv/usr/src/suites/os/smf/tests/svccfg/doc/ |
| ASSERTIONS | 108 binary file, non-existent file, directory, device.
927 binary file, non-existent file, directory, device.
1144 binary file, non-existent file, directory, device.
[all...] |
| /test/stcnv/usr/src/suites/fs/share/ |
| README | 176 In addition, test suite binary packages can be constructed using the
|
| /test/stcnv/usr/src/suites/net/nc/ |
| README | 226 If you need to test nc binary which is not in default location (for
|
