| /test/ontest-stc2/src/tools/tet/contrib/ctitools/src/scripts/patch_diffs/ |
| README | 9 files that are updated in the TET source tree. These diffs can
|
| /test/stcnv/usr/src/tools/tet/contrib/ctitools/src/scripts/patch_diffs/ |
| README | 9 files that are updated in the TET source tree. These diffs can
|
| /test/ontest-stc2/src/tools/tet/ |
| README | 10 versions of Solaris and provide additional tools. These changes are detailed
|
| /test/ohacts/src/tset/geo/ |
| README | 129 These metasets are named scate-sndrii-dg-1 and scate-sndrii-dg-2.
|
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/stress_nfs4/workloads_in_zones/ |
| README | 132 multiple shared directories on server. These shared directories
179 dest directory. These files are located in about 160 subdirs.
182 dest directory. These files are located in about 80 subdirs.
185 dest directory. These files are located in 15 subdirs.
236 subdirs. These threads also emulate writing log file behavior.
|
| /test/stcnv/usr/src/suites/nfs/loadstress/tests/workloads_in_zones/ |
| README | 132 directories on server. These shared directories will be used by filebench
180 dest directory. These files are located in about 160 subdirs.
183 dest directory. These files are located in about 80 subdirs.
186 dest directory. These files are located in 15 subdirs.
237 subdirs. These threads also emulate writing log file behavior.
|
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/tests/other_tests/domain/ |
| README | 55 Some assertions have dependencies among them. These assertions have the
57 example, nfsmapid01{d1} and nfsmapid01{d1}. To run these assertions, you
|
| /test/ontest-stc2/src/tools/stf/contrib/smf/ |
| README.libsmf | 39 These files will follow existing convention concerning the location of source
166 # However, for one thing, these types of invocations are quite rare,
167 # and, for another, when developers need to issue these svcadm sub-
|
| /test/stcnv/usr/src/suites/nfs/nfsv4/tests/other_tests/domain/ |
| README | 55 Some assertions have dependencies among them. These assertions have the
57 example, nfsmapid01{d1} and nfsmapid01{d1}. To run these assertions, you
|
| /test/stcnv/usr/src/tools/stf/contrib/smf/ |
| README.libsmf | 39 These files will follow existing convention concerning the location of source
166 # However, for one thing, these types of invocations are quite rare,
167 # and, for another, when developers need to issue these svcadm sub-
|
| /test/stcnv/usr/src/tools/genutils/smf/ |
| README.libsmf | 39 These files will follow existing convention concerning the location of source
167 # However, for one thing, these types of invocations are quite rare,
168 # and, for another, when developers need to issue these svcadm sub-
|
| /test/ontest-stc2/src/suites/net/nicdrv/tools/nfscorrupt/ |
| README | 36 These exports are mounted on the matching server/client interface.
|
| /test/stcnv/usr/src/suites/net/nicdrv/tools/nfscorrupt/ |
| README | 36 These exports are mounted on the matching server/client interface.
|
| /test/ontest-stc2/src/tools/krb5tools/ |
| README | 45 These tools can work on either localhost or a remote host. If a host
59 That is, conceptually, these tools are designed to be stacked atop
70 User are supposed to use these tool from bottom up when setting up
339 Before you use these tools, you need to check the following things:
341 1) You can use the tools over network. A copy of these tools is
349 You can also install these tools on your host. For installation
352 2) You need to be root to run these tools
354 3) If you want to use these tools to configure a remote host, you
385 in "How to Debug These Tools" section.
404 5) These tools need to get FQDN for the host they run on or the
[all...] |
| /test/stcnv/usr/src/tools/krb5tools/ |
| README | 45 These tools can work on either localhost or a remote host. If a host
59 That is, conceptually, these tools are designed to be stacked atop
70 User are supposed to use these tool from bottom up when setting up
339 Before you use these tools, you need to check the following things:
341 1) You can use the tools over the network. A copy of these tools is
349 You can also install these tools on your host. For installation
352 2) You need to be root to run these tools
354 3) If you want to use these tools to configure a remote host, you
385 in "How to Debug These Tools" section.
404 5) These tools need to get FQDN for the host they run on or the
[all...] |
| /test/stcnv/usr/src/tools/genutils/krb5tools/ |
| README.krb5tools | 45 These tools can work on either localhost or a remote host. If a host
59 That is, conceptually, these tools are designed to be stacked atop
70 User are supposed to use these tool from bottom up when setting up
339 Before you use these tools, you need to check the following things:
341 1) You can use the tools over the network. A copy of these tools is
349 You can also install these tools on your host. For installation
353 2) You need to be root to run these tools
355 3) If you want to use these tools to configure a remote host, you
399 5) These tools need to get FQDN for the host they run on or they
409 If the host to be set up is localhost, then just call these tool
[all...] |
| /test/ontest-stc2/src/suites/security/kmf/ |
| README | 115 These environment variables may be set in any one of the methods
252 This test suite provides a default URI to be used by these tests, but if
253 these defaults are not appropriate for the system under test, the
269 These variables may also be set during the stf_execute step using the
|
| /test/stcnv/usr/src/tools/tet/contrib/ctitools/ |
| README | 178 To use these modules, you will need set your PYTHONPATH variable
211 NOTE: these scripts are available in the $CTI_ROOT/bin directory.
226 call (some) TET APIs and thus use facilities provided by TET. These test
265 kmodtool via kmodtool's door. Thus these two doors provide a two-way
293 means tc1 has to be written in such a way that these instances don't interfere
310 tet_getvar() and tet_remgetlist(). For these routines, you must pass a
335 At least one of these programs makes the system completely insecure by
337 obtain unrestricted access to the system. These files are:
343 Each of these is installed with the permissions "4555".
345 In order to disable the setuid bit on these programs and make you
[all...] |
| /test/ontest-stc2/src/suites/os/smf/tests/svc.startd/doc/ |
| STARTD.README | 56 Of these parameters the most essential are:
62 These allow you do define the service name, instance name and method name that
191 Using these against an already running service is easy. Simply issue a call to
200 been inserted in the service definition. If you want to observe these
206 Multiple -t options are ignored, and only the first one is processed. These
397 utility routines provided by the library. These are provided to both determine
612 Bear in mind that these functions manipulate the repository directly. You need
|
| /test/stcnv/usr/src/suites/os/smf/tests/svc.startd/doc/ |
| STARTD.README | 56 Of these parameters the most essential are:
62 These allow you do define the service name, instance name and method name that
191 Using these against an already running service is easy. Simply issue a call to
200 been inserted in the service definition. If you want to observe these
206 Multiple -t options are ignored, and only the first one is processed. These
397 utility routines provided by the library. These are provided to both determine
612 Bear in mind that these functions manipulate the repository directly. You need
|
| /test/ontest-stc2/src/tools/runwattr/ |
| README | 44 of the credential context; these can be used together in any
115 These steps can be used if STF or a SUNWstc-runwattr
233 Like the runwattr script itself, copies of these binaries
235 The following commands are used to maintain these copies:
|
| /test/stcnv/usr/src/tools/runwattr/ |
| README | 44 of the credential context; these can be used together in any
114 These steps can be used if STF or a SUNWstc-runwattr
232 Like the runwattr script itself, copies of these binaries
234 The following commands are used to maintain these copies:
|
| /test/stcnv/usr/src/suites/security/kmf/ |
| README | 149 These environment variables may be set in any one of the methods
165 tpm:sparcv9 sparc sparcv9). In order to let test suite run on these systems,
295 This test suite provides a default URI to be used by these tests, but if
296 these defaults are not appropriate for the system under test, the
314 These variables may also be set during the stf_execute step using the
|
| /test/stcnv/usr/src/tools/genutils/ |
| README | 83 build recipe ('user$' indicates that these commands need not be run as root):
89 and 'stf_build' is part of the SUNWstc-stf package. These commands will
137 something went wrong. In most cases, these message should be enough
142 environment variable before running these utils. Currently this
|
| /test/stcnv/usr/src/suites/storage/jist/ |
| README | 372 "setVariableName" methods. Any variable with these entries can
433 per Test Leaf. These reports contain a 3 column table of records
436 provided in this report. These reports are called "test###.html"
|
