Print this page
nits pt 2
Fix nits
Updated wording
5032 share_nfs(1m): Documentation for "noaclfab" is needed

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man1m/share_nfs.1m.man.txt
          +++ new/usr/src/man/man1m/share_nfs.1m.man.txt
↓ open down ↓ 92 lines elided ↑ open up ↑
  93   93                 log[=tag]
  94   94                           Enables NFS server logging for the specified file
  95   95                           system. The optional tag determines the location of
  96   96                           the related log files. The tag is defined in
  97   97                           /etc/nfs/nfslog.conf.  If no tag is specified, the
  98   98                           default values associated with the global tag in
  99   99                           /etc/nfs/nfslog.conf are used. Support of NFS server
 100  100                           logging is only available for NFS Version 2 and
 101  101                           Version 3 requests.
 102  102  
      103 +               noaclfab  By default, the NFS server will fabricate POSIX-draft
      104 +                         style ACLs in response to ACL requests from NFS
      105 +                         Version 2 or Version 3 clients accessing shared file
      106 +                         systems that do not support POSIX-draft ACLs (such as
      107 +                         ZFS).  Specifying noaclfab disables this behavior.
      108 +
 103  109                 none=access_list
 104  110                           Access is not allowed to any client that matches the
 105  111                           access list. The exception is when the access list is
 106  112                           an asterisk (*), in which case ro or rw can override
 107  113                           none.
 108  114  
 109  115                 nosub     Prevents clients from mounting subdirectories of
 110  116                           shared directories. For example, if /export is shared
 111  117                           with the nosub option on server "fooey" then a NFS
 112  118                           client cannot do:
↓ open down ↓ 233 lines elided ↑ open up ↑
 346  352       command line does not start the nfslogd(1M).
 347  353  
 348  354     Example 2 Remap A User Coming From The Particular NFS Client
 349  355       The following example remaps the user with uid 100 at client 10.0.0.1 to
 350  356       user joe:
 351  357  
 352  358             share -o uidmap=100:joe:@10.0.0.1 /export
 353  359  
 354  360  SEE ALSO
 355  361       mount(1M), mountd(1M), nfsd(1M), nfslogd(1M), share(1M), unshare(1M),
 356      -     getnetbyname(3SOCKET), netgroup(4), nfslog.conf(4), attributes(5),
 357      -     nfssec(5)
      362 +     getnetbyname(3SOCKET), netgroup(4), nfslog.conf(4), acl(5),
      363 +     attributes(5), nfssec(5)
 358  364  
 359  365  NOTES
 360  366       If the sec= option is presented at least once, all uses of the window=,
 361  367       rw, ro, rw=, ro=, and root= options must come after the first sec=
 362  368       option. If the sec= option is not presented, then sec=sys is implied.
 363  369  
 364  370       If one or more explicit sec= options are presented, sys must appear in
 365  371       one of the options mode lists for accessing using the AUTH_SYS security
 366  372       mode to be allowed. For example:
 367  373  
↓ open down ↓ 95 lines elided ↑ open up ↑
 463  469       a symbolic link.  This allows the processing of paths that are not
 464  470       themselves explicitly shared with share_nfs.  For example, /export/foo
 465  471       might be a symbolic link that refers to /export/bar which has been
 466  472       specifically shared. When the client mounts /export/foo the mountd
 467  473       processing follows the symbolic link and responds with the /export/bar.
 468  474       The NFS Version 4 protocol does not use the mountd processing and the
 469  475       client's use of /export/foo does not work as it does with NFS Version 2
 470  476       and Version 3 and the client receives an error when attempting to mount
 471  477       /export/foo.
 472  478  
 473      -illumos                        November 10, 2014                       illumos
      479 +illumos                        December 16, 2016                       illumos
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX