83 The gidmap= option is evaluated before the anon=
84 option.
85
86 This option is supported only for AUTH_SYS.
87
88 index=file
89 Load file rather than a listing of the directory
90 containing this file when the directory is referenced
91 by an NFS URL.
92
93 log[=tag]
94 Enables NFS server logging for the specified file
95 system. The optional tag determines the location of
96 the related log files. The tag is defined in
97 /etc/nfs/nfslog.conf. If no tag is specified, the
98 default values associated with the global tag in
99 /etc/nfs/nfslog.conf are used. Support of NFS server
100 logging is only available for NFS Version 2 and
101 Version 3 requests.
102
103 none=access_list
104 Access is not allowed to any client that matches the
105 access list. The exception is when the access list is
106 an asterisk (*), in which case ro or rw can override
107 none.
108
109 nosub Prevents clients from mounting subdirectories of
110 shared directories. For example, if /export is shared
111 with the nosub option on server "fooey" then a NFS
112 client cannot do:
113
114 mount -F nfs fooey:/export/home/mnt
115
116 NFS Version 4 does not use the MOUNT protocol. The
117 nosub option only applies to NFS Version 2 and
118 Version 3 requests.
119
120 nosuid By default, clients are allowed to create files on
121 the shared file system with the setuid or setgid mode
122 enabled. Specifying nosuid causes the server file
336 enabled:
337
338 share -o log /export
339
340 The default global logging parameters are used since no tag identifier is
341 specified. The location of the log file, as well as the necessary logging
342 work files, is specified by the global entry in /etc/nfs/nfslog.conf.
343 The nfslogd(1M) daemon runs only if at least one file system entry in
344 /etc/dfs/dfstab is shared with logging enabled upon starting or rebooting
345 the system. Simply sharing a file system with logging enabled from the
346 command line does not start the nfslogd(1M).
347
348 Example 2 Remap A User Coming From The Particular NFS Client
349 The following example remaps the user with uid 100 at client 10.0.0.1 to
350 user joe:
351
352 share -o uidmap=100:joe:@10.0.0.1 /export
353
354 SEE ALSO
355 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)
358
359 NOTES
360 If the sec= option is presented at least once, all uses of the window=,
361 rw, ro, rw=, ro=, and root= options must come after the first sec=
362 option. If the sec= option is not presented, then sec=sys is implied.
363
364 If one or more explicit sec= options are presented, sys must appear in
365 one of the options mode lists for accessing using the AUTH_SYS security
366 mode to be allowed. For example:
367
368 share -F nfs /var
369 share -F nfs -o sec=sys /var
370
371 grants read-write access to any host using AUTH_SYS, but
372
373 share -F nfs -o sec=dh /var
374
375 grants no access to clients that use AUTH_SYS.
376
377 Unlike previous implementations of share_nfs, access checking for the
453
454 share -F nfs -o ro /disk
455
456 The same command entered from the command line does not share the /disk
457 file system unless there is at least one file system entry in the
458 /etc/dfs/dfstab file. The mountd(1M) and nfsd(1M) daemons only run if
459 there is a file system entry in /etc/dfs/dfstab when starting or
460 rebooting the system.
461
462 The mountd(1M) process allows the processing of a path name the contains
463 a symbolic link. This allows the processing of paths that are not
464 themselves explicitly shared with share_nfs. For example, /export/foo
465 might be a symbolic link that refers to /export/bar which has been
466 specifically shared. When the client mounts /export/foo the mountd
467 processing follows the symbolic link and responds with the /export/bar.
468 The NFS Version 4 protocol does not use the mountd processing and the
469 client's use of /export/foo does not work as it does with NFS Version 2
470 and Version 3 and the client receives an error when attempting to mount
471 /export/foo.
472
473 illumos November 10, 2014 illumos
|
83 The gidmap= option is evaluated before the anon=
84 option.
85
86 This option is supported only for AUTH_SYS.
87
88 index=file
89 Load file rather than a listing of the directory
90 containing this file when the directory is referenced
91 by an NFS URL.
92
93 log[=tag]
94 Enables NFS server logging for the specified file
95 system. The optional tag determines the location of
96 the related log files. The tag is defined in
97 /etc/nfs/nfslog.conf. If no tag is specified, the
98 default values associated with the global tag in
99 /etc/nfs/nfslog.conf are used. Support of NFS server
100 logging is only available for NFS Version 2 and
101 Version 3 requests.
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
109 none=access_list
110 Access is not allowed to any client that matches the
111 access list. The exception is when the access list is
112 an asterisk (*), in which case ro or rw can override
113 none.
114
115 nosub Prevents clients from mounting subdirectories of
116 shared directories. For example, if /export is shared
117 with the nosub option on server "fooey" then a NFS
118 client cannot do:
119
120 mount -F nfs fooey:/export/home/mnt
121
122 NFS Version 4 does not use the MOUNT protocol. The
123 nosub option only applies to NFS Version 2 and
124 Version 3 requests.
125
126 nosuid By default, clients are allowed to create files on
127 the shared file system with the setuid or setgid mode
128 enabled. Specifying nosuid causes the server file
342 enabled:
343
344 share -o log /export
345
346 The default global logging parameters are used since no tag identifier is
347 specified. The location of the log file, as well as the necessary logging
348 work files, is specified by the global entry in /etc/nfs/nfslog.conf.
349 The nfslogd(1M) daemon runs only if at least one file system entry in
350 /etc/dfs/dfstab is shared with logging enabled upon starting or rebooting
351 the system. Simply sharing a file system with logging enabled from the
352 command line does not start the nfslogd(1M).
353
354 Example 2 Remap A User Coming From The Particular NFS Client
355 The following example remaps the user with uid 100 at client 10.0.0.1 to
356 user joe:
357
358 share -o uidmap=100:joe:@10.0.0.1 /export
359
360 SEE ALSO
361 mount(1M), mountd(1M), nfsd(1M), nfslogd(1M), share(1M), unshare(1M),
362 getnetbyname(3SOCKET), netgroup(4), nfslog.conf(4), acl(5),
363 attributes(5), nfssec(5)
364
365 NOTES
366 If the sec= option is presented at least once, all uses of the window=,
367 rw, ro, rw=, ro=, and root= options must come after the first sec=
368 option. If the sec= option is not presented, then sec=sys is implied.
369
370 If one or more explicit sec= options are presented, sys must appear in
371 one of the options mode lists for accessing using the AUTH_SYS security
372 mode to be allowed. For example:
373
374 share -F nfs /var
375 share -F nfs -o sec=sys /var
376
377 grants read-write access to any host using AUTH_SYS, but
378
379 share -F nfs -o sec=dh /var
380
381 grants no access to clients that use AUTH_SYS.
382
383 Unlike previous implementations of share_nfs, access checking for the
459
460 share -F nfs -o ro /disk
461
462 The same command entered from the command line does not share the /disk
463 file system unless there is at least one file system entry in the
464 /etc/dfs/dfstab file. The mountd(1M) and nfsd(1M) daemons only run if
465 there is a file system entry in /etc/dfs/dfstab when starting or
466 rebooting the system.
467
468 The mountd(1M) process allows the processing of a path name the contains
469 a symbolic link. This allows the processing of paths that are not
470 themselves explicitly shared with share_nfs. For example, /export/foo
471 might be a symbolic link that refers to /export/bar which has been
472 specifically shared. When the client mounts /export/foo the mountd
473 processing follows the symbolic link and responds with the /export/bar.
474 The NFS Version 4 protocol does not use the mountd processing and the
475 client's use of /export/foo does not work as it does with NFS Version 2
476 and Version 3 and the client receives an error when attempting to mount
477 /export/foo.
478
479 illumos December 16, 2016 illumos
|