Print this page
    
Marcel's code review fixes
Marcel's update to 7651
    
      
        | Split | 
	Close | 
      
      | Expand all | 
      | Collapse all | 
    
    
          --- old/usr/src/man/man4/nfs.4.man.txt
          +++ new/usr/src/man/man4/nfs.4.man.txt
   1    1  NFS(4)                  File Formats and Configurations                 NFS(4)
   2    2  
   3    3  NAME
   4    4       nfs - NFS configuration properties
   5    5  
   6    6  DESCRIPTION
   7    7       The behavior of the nfsd(1M), nfsmapid(1M), lockd(1M), and mountd(1M)
   8    8       daemons and mount_nfs(1M) command is controlled by property values that
   9    9       are stored in the Service Management Facility, smf(5). The sharectl(1M)
  10   10       command should be used to query or change values for these properties.
  11   11  
  12   12       Changes made to nfs property values on the nfsd, lockd, mountd, or
  13   13       mount_nfs command line override the values set using sharectl(1M).
  14   14  
  15   15       The following list describes the properties:
  16   16  
  17   17       client_versmin=num
  18   18       client_versmax=num
  19   19               The NFS client only uses NFS versions in the range specified by
  20   20               these properties. Valid values of versions are: 2, 3, and 4.
  21   21               Default minimum version is 2, while default maximum is 4.
  22   22  
  23   23               You can override this range on a per-mount basis by using the -o
  24   24               vers= option to mount_nfs(1M).
  25   25  
  26   26       server_versmin=num
  27   27       server_versmax=num
  28   28               The NFS server only uses NFS versions in the range specified by
  29   29               these properties. Valid values of versions are: 2, 3, and 4.
  30   30               Default minimum version is 2, while the default maximum version
  31   31               is 4.
  32   32  
  33   33       server_delegation=on|off
  34   34               By default the NFS server provides delegations to clients. The
  35   35               user can turn off delegations for all exported filesystems by
  36   36               setting this variable to off.  This variable only applies to NFS
  37   37               Version 4.
  38   38  
  39   39       nfsmapid_domain=[string]
  40   40               By default, the nfsmapid uses the DNS domain of the system. This
  41   41               setting overrides the default. This domain is used for
  42   42               identifying user and group attribute strings in the NFS Version 4
  43   43               protocol. Clients and servers must match with this domain for
  44   44               operation to proceed normally. This variable only applies to NFS
  45   45               Version 4. See Setting nfsmapid_domain below for further details.
  46   46  
  47   47       max_connections=num
  48   48               Sets the maximum number of concurrent, connection-oriented
  49   49               connections. The default is -1 (unlimited).  Equivalent to the -c
  50   50               option in nfsd.
  51   51  
  52   52       listen_backlog=num
  53   53               Set connection queue length for the NFS over a connection-
  54   54               oriented transport.  The default value is 32, meaning 32 entries
  55   55               in the queue. Equivalent to the -l option in nfsd.
  56   56  
  57   57       protocol=[all|protocol]
  58   58               Start nfsd over the specified protocol only. Equivalent to the -p
  59   59               option in nfsd.  all is equivalent to -a on the nfsd command
  60   60               line. Mutually exlusive of device.  For the UDP protocol, only
  
    | 
      ↓ open down ↓ | 
    60 lines elided | 
    
      ↑ open up ↑ | 
  
  61   61               version 2 and version 3 service is established. NFS Version 4 is
  62   62               not supported for the UDP protocol.
  63   63  
  64   64       device=[devname]
  65   65               Start NFS daemon for the transport specified by the given device
  66   66               only.  Equivalent to the -t option in nfsd.  Mutually exclusive
  67   67               of protocol.
  68   68  
  69   69       servers=num
  70   70               Maximum number of concurrent NFS requests. Equivalent to last
  71      -             numeric argument on the nfsd command line. The default is 16.
       71 +             numeric argument on the nfsd command line. The default is 1024.
  72   72  
  73   73       lockd_listen_backlog=num
  74   74               Set connection queue length for lockd over a connection-oriented
  75   75               transport. The default and minimum value is 32.
  76   76  
  77   77       lockd_servers=num
  78      -             Maximum number of concurrent lockd requests. The default is 20.
       78 +             Maximum number of concurrent lockd requests. The default is 256.
  79   79  
  80   80       lockd_retransmit_timeout=num
  81   81               Retransmit timeout, in seconds, before lockd retries. The default
  82   82               is 5.
  83   83  
  84   84       grace_period=num
  85   85               Grace period, in seconds, that all clients (both NLM and NFSv4)
  86   86               have to reclaim locks after a server reboot. This parameter also
  87   87               controls the NFSv4 lease interval. The default is 90.
  88   88  
  89   89       mountd_listen_backlog=num
  90   90               Set the connection queue length for mountd over a connection-
  91   91               oriented transport. The default value is 64.
  92   92  
  93   93       mountd_max_threads=num
  94   94               Maximum number of threads for mountd.  The default value is 16.
  95   95  
  96   96     Setting nfsmapid_domain
  97   97       As described above, the setting for nfsmapid_domain overrides the domain
  98   98       used by nfsmapid(1M) for building and comparing outbound and inbound
  99   99       attribute strings, respectively.  This setting overrides any other
 100  100       mechanism for setting the NFSv4 domain. In the absence of a
 101  101       nfsmapid_domain setting, the nfsmapid(1M) daemon determines the NFSv4
 102  102       domain as follows:
 103  103  
 104  104       o   If a properly configured /etc/resolv.conf (see resolv.conf(4))
 105  105           exists, nfsmapid queries specified nameserver(s) for the domain.
 106  106  
 107  107       o   If a properly configured /etc/resolv.conf (see resolv.conf(4))
 108  108           exists, but the queried nameserver does not have a proper record of
 109  109           the domain name, nfsmapid attempts to obtain the domain name through
 110  110           the BIND interface (see resolver(3RESOLV)).
 111  111  
 112  112       o   If no /etc/resolv.conf exists, nfsmapid falls back on using the
 113  113           configured domain name (see domainname(1M)), which is returned with
 114  114           the leading domain suffix removed. For example, for
 115  115           widgets.sales.acme.com, sales.acme.com is returned.
 116  116  
 117  117       o   If /etc/resolv.conf does not exist, no domain name has been
 118  118           configured (or no /etc/defaultdomain exists), nfsmapid falls back on
 119  119           obtaining the domain name from the host name, if the host name
 120  120           contains a fully qualified domain name (FQDN).
 121  121  
 122  122       If a domainname is still not obtained following all of the preceding
 123  123       steps, nfsmapid will have no domain configured. This results in the
 124  124       following behavior:
 125  125  
 126  126       o   Outbound "owner" and "owner_group" attribute strings are encoded as
 127  127           literal id's. For example, the UID 12345 is encoded as 12345.
 128  128  
 129  129       o   nfsmapid ignores the "domain" portion of the inbound attribute string
 130  130           and performs name service lookups only for the user or group. If the
 131  131           user/group exists in the local system name service databases, then
 132  132           the proper uid/gid will be mapped even when no domain has been
 133  133           configured.
 134  134  
 135  135           This behavior implies that the same administrative user/group domain
 136  136           exists between NFSv4 client and server (that is, the same uid/gid's
  
    | 
      ↓ open down ↓ | 
    48 lines elided | 
    
      ↑ open up ↑ | 
  
 137  137           for users/groups on both client and server). In the case of
 138  138           overlapping id spaces, the inbound attribute string could potentially
 139  139           be mapped to the wrong id. However, this is not functionally
 140  140           different from mapping the inbound string to nobody, yet provides
 141  141           greater flexibility.
 142  142  
 143  143  SEE ALSO
 144  144       lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
 145  145       sharectl(1M), smf(5)
 146  146  
 147      -illumos                        November 16, 2016                       illumos
      147 +illumos                        December 16, 2016                       illumos
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX