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

1 2

  /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/nfsgen/tests/acl/
README 30 There are two subdirs:
  /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/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/create_port/
ASSERTIONS 55 DESCRIPTION: There are 5 parameters for function FCOE_CreatePort(), it
77 DESCRIPTION: There are 5 parameters for function FCOE_CreatePort(), it
145 DESCRIPTION: There are 5 parameters for function FCOE_CreatePort(), it
168 DESCRIPTION: There are 5 parameters for function FCOE_CreatePort(), it
  /test/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/delete_port/
ASSERTIONS 60 DESCRIPTION: There are only one parameters for function FCOE_DeletePort(),
83 DESCRIPTION: There are only one parameters for function FCOE_DeletePort(),
  /test/stcnv/usr/src/suites/storage/comstar/tests/fcoe/libfcoe/get_port_list/
ASSERTIONS 76 DESCRIPTION: There should be a failure if NULL is passed as first parameter
98 DESCRIPTION: There should be a failure if NULL is passed as second parameter
  /test/ontest-stc2/src/suites/security/sbd/
README 158 There will be an STF journal file, a log file from the SMF service
200 contain useful debug information only. There's no explicit PASS in the
  /test/stcnv/usr/src/suites/security/sbd/
README 157 There will be an STF journal file, a log file from the SMF service
199 contain useful debug information only. There's no explicit PASS in the
  /test/ontest-stc2/src/suites/os/xvm/virt-install/
README.CONFIG 30 up a valid test_config file for the virt-install test suite. There
62 - test suite execution (DO NOT CHANGE ANYTHING THERE)
README 169 There is no need for any unconfigure to be run after the test suite
  /test/stcnv/usr/src/suites/os/xvm/virt-install/
README.CONFIG 30 up a valid test_config file for the virt-install test suite. There
56 - test suite execution (DO NOT CHANGE ANYTHING THERE)
  /test/ontest-stc2/src/tools/krb5tools/bin/
princadm.ksh 84 There can be multiple -p options.
kdc_clientcfg.ksh 91 There can be multiple -p options.
215 # if localhost and $kdc are the same host, there is no need to set up.
  /test/stcnv/usr/src/tools/genutils/krb5tools/bin/
princadm.ksh 87 There can be multiple -p options.
kdc_clientcfg.ksh 94 There can be multiple -p options.
223 # if localhost and $kdc are the same host, there is no need to set up.
  /test/stcnv/usr/src/tools/krb5tools/bin/
princadm.ksh 84 There can be multiple -p options.
kdc_clientcfg.ksh 91 There can be multiple -p options.
214 # if localhost and $kdc are the same host, there is no need to set up.
  /test/stcnv/usr/src/suites/nfs/loadstress/
README 40 There is no hareware requirement for running this test sutie; however,
  /test/ontest-stc2/src/suites/iSCSI/
README 41 2. There should be no iscsi targets configured via the iscsitadm
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-mid/property/
README_XML 32 There are three manifest files defining the instances:
204 There are 39 properties.
  /test/ontest-stc2/src/suites/os/smf/tests/libscf-mid/property/scf_simple_prop_get/
ASSERTIONS 261 There is a partially developed test for this assertion, but it
  /test/stcnv/usr/src/suites/os/smf/tests/libscf-mid/property/
README_XML 32 There are three manifest files defining the instances:
204 There are 39 properties.
  /test/stcnv/usr/src/suites/os/smf/tests/libscf-mid/property/scf_simple_prop_get/
ASSERTIONS 261 There is a partially developed test for this assertion, but it
  /test/stcnv/usr/src/tools/diskomizer/
README 52 There are two ways to build Diskomizer.
  /test/ontest-stc2/src/suites/os/smf/tests/svc.startd/doc/
STARTD.README 70 There are 3 pre-defined methods:
86 If there are no service processes, then the service would be reported
366 purpose there is the 'manifest_generate' function in the test library. This
371 Before you import the file into the registry you need to make sure that there
374 the repository already. There is a function called manifest_purgemd5, which
450 the entry was matched in the log. there is a utility function:
509 - make sure there's no service state lingering in the repository
511 - make sure there's no historic manifest checksum in the system.

Completed in 6598 milliseconds

1 2