132      steps, nfsmapid will have no domain configured.  This results in the
 133      following behavior:
 134 
 135      o   Outbound "owner" and "owner_group" attribute strings are encoded as
 136          literal id's.  For example, the UID 12345 is encoded as 12345.
 137 
 138      o   nfsmapid ignores the "domain" portion of the inbound attribute string
 139          and performs name service lookups only for the user or group.  If the
 140          user/group exists in the local system name service databases, then
 141          the proper uid/gid will be mapped even when no domain has been
 142          configured.
 143 
 144          This behavior implies that the same administrative user/group domain
 145          exists between NFSv4 client and server (that is, the same uid/gid's
 146          for users/groups on both client and server).  In the case of
 147          overlapping id spaces, the inbound attribute string could potentially
 148          be mapped to the wrong id.  However, this is not functionally
 149          different from mapping the inbound string to nobody, yet provides
 150          greater flexibility.
 151 









 152 SEE ALSO
 153      lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
 154      sharectl(1M), smf(5)
 155 
 156 illumos                        December 18, 2016                       illumos

 132      steps, nfsmapid will have no domain configured.  This results in the
 133      following behavior:
 134 
 135      o   Outbound "owner" and "owner_group" attribute strings are encoded as
 136          literal id's.  For example, the UID 12345 is encoded as 12345.
 137 
 138      o   nfsmapid ignores the "domain" portion of the inbound attribute string
 139          and performs name service lookups only for the user or group.  If the
 140          user/group exists in the local system name service databases, then
 141          the proper uid/gid will be mapped even when no domain has been
 142          configured.
 143 
 144          This behavior implies that the same administrative user/group domain
 145          exists between NFSv4 client and server (that is, the same uid/gid's
 146          for users/groups on both client and server).  In the case of
 147          overlapping id spaces, the inbound attribute string could potentially
 148          be mapped to the wrong id.  However, this is not functionally
 149          different from mapping the inbound string to nobody, yet provides
 150          greater flexibility.
 151 
 152 ZONES
 153      NFS can be served out of a non-global zone.  All of the above
 154      documentation applies to an in-zone NFS server.  File sharing in zones is
 155      restricted to filesystems a zone completely controls.  Some zone brands
 156      (see brands(5)) do not give the zone's root its own filesystem, for
 157      example.  Delegated ZFS datasets to a zone are shareable, as well as
 158      lofs-remounted directories.  The zone must have sys_nfs privileges; most
 159      brands grant this already.
 160 
 161 SEE ALSO
 162      lockd(1M), mount_nfs(1M), mountd(1M), nfsd(1M), nfsmapid(1M),
 163      sharectl(1M), brands(5), smf(5), zones(5)
 164 
 165 illumos                        February 4, 2020                        illumos