Print this page
12278 nfs-zone needs man page changes
Reviewed by: Peter Tribble <peter.tribble@gmail.com>
Reviewed by: Gordon Ross <gordon.w.ross@gmail.com>
*** 87,104 ****
1 Daemon failed to start.
SEE ALSO
svcs(1), mountd(1M), share(1M), sharectl(1M), sharemgr(1M), svcadm(1M),
! nfs(4), sharetab(4), system(4), attributes(5), smf(5)
NOTES
Manually starting and restarting nfsd is not recommended. If it is
necessary to do so, use svcadm to enable or disable the nfs service
(svc:/network/nfs/server). If it is disabled, it will be enabled by
share_nfs(1M), unless its application/auto_enable property is set to
! false. See the , and svcadm(1M) for more information.
The nfsd service is managed by the service management facility, smf(5),
under the service identifier:
svc:/network/nfs/server
--- 87,104 ----
1 Daemon failed to start.
SEE ALSO
svcs(1), mountd(1M), share(1M), sharectl(1M), sharemgr(1M), svcadm(1M),
! nfs(4), sharetab(4), system(4), attributes(5), smf(5), zones(5)
NOTES
Manually starting and restarting nfsd is not recommended. If it is
necessary to do so, use svcadm to enable or disable the nfs service
(svc:/network/nfs/server). If it is disabled, it will be enabled by
share_nfs(1M), unless its application/auto_enable property is set to
! false. See smf(5) and svcadm(1M) for more information.
The nfsd service is managed by the service management facility, smf(5),
under the service identifier:
svc:/network/nfs/server
*** 109,114 ****
If nfsd is killed with SIGTERM, it will not be restarted by the service
management facility. Instead, nfsd can be restarted by other signals,
such as SIGINT.
! illumos March 12, 2016 illumos
--- 109,117 ----
If nfsd is killed with SIGTERM, it will not be restarted by the service
management facility. Instead, nfsd can be restarted by other signals,
such as SIGINT.
! NFS service, which includes nfsd, can run inside a non-global zone. See
! the discussion under ZONES in nfs(4) for more information.
!
! illumos February 4, 2020 illumos