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