1 #
   2 # CDDL HEADER START
   3 #
   4 # The contents of this file are subject to the terms of the
   5 # Common Development and Distribution License (the "License").
   6 # You may not use this file except in compliance with the License.
   7 #
   8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
   9 # See the License for the specific language governing permissions
  10 # and limitations under the License.
  11 #
  12 # When distributing Covered Code, include this CDDL HEADER in each
  13 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  14 # If applicable, add the following below this CDDL HEADER, with the
  15 # fields enclosed by brackets "[]" replaced with your own identifying
  16 # information: Portions Copyright [yyyy] [name of copyright owner]
  17 #
  18 # CDDL HEADER END
  19 #
  20 
  21 #
  22 # Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
  23 # Use is subject to license terms.
  24 #
  25 # nfsv4-test/tests/other_tests/domain/README
  26 #
  27 
  28 This sub-suite consists of tests for testing rules to get the domain for
  29 NFSv4 NFSMAPID.
  30 
  31 1. How to Run Assertions
  32 ========================
  33 
  34 To run all assertions, just follow nfsv4-test suite convention and use the 
  35 following command:
  36 
  37     ./runtests
  38 
  39 To run specific assertions, use the following command:
  40         
  41     TESTLIST=<test_file> ASSERTIONS="<assertion_name> ..." ./runtests
  42 
  43 Example 1: the following command runs nfsmapid01{a}
  44 
  45     TESTLIST=nfsmapid01 ASSERTIONS="a" ./runtests
  46 
  47 Example 2: the following command runs libmapid01{a}, libmapid01{b}, and 
  48 libmapid01{c}
  49 
  50     TESTLIST=libmapid01 ASSERTIONS="a b c" ./runtests
  51 
  52 Some assertions have dependencies among them. These assertions have the 
  53 same name, but with a different numeric character appended to it, for 
  54 example, nfsmapid01{d1} and nfsmapid01{d1}. To run these assertions, you
  55 need to remove the numeric postfix:
  56 
  57 Example 3: the following command runs nfsmapid01{d1} and nfsmapid02{d2}
  58 
  59     TESTLIST=nfsmapid01 ASSERTIONS="d" ./runtests
  60 
  61 
  62 2. nfscfg_domain_tmout
  63 ======================
  64 
  65 nfsmapid(1M) has a nfscfg_domain_tmout variable to control how long the 
  66 daemon thread waits before it checks domain configuration changes. Its value
  67 is 300 seconds by default. 
  68 
  69 Using that default value, it takes more than 1 hour to run all tests. So, 
  70 to make them run faster, the value is changed to 10 seconds during the test.
  71 
  72 User can customize this value with DOMAIN_TMOUT env variable, in the 
  73 following way:
  74 
  75     DOMAIN_TMOUT=60 ./runtests
  76 
  77 Please note the above method only works in global zone and whole root zone.
  78 The reason is we do that by using mdb to modify nfsmapid(1M) binary file.
  79 In sparse root zone, however, the file is on a file system shared with
  80 read-only option, so the value of nfscfg_domain_tmout variable can't be 
  81 changed.
  82 
  83 So it takes much longer(more than 1 hour) to run all tests in sparse root zone.