NFS Services Administrator's Guide (B1031-90072, March 2011)

Changes to the NFS Server Daemon
The NFS server daemon (nfsd) handles client filesystem requests. By default, nfsd starts over
TCP and UDP for NFSv2 and NFSv3. If NFSv4 is enabled, the nfsd daemon is started to service
all TCP and UDP requests.
If you want to change startup parameters for nfsd, you must login as superuser (root) and make
changes to the /etc/default/nfs file or use the setoncenv command.
The /etc/default/nfs file provides startup parameters for the nfsd daemon and rpc.lockd
daemon. For more information on the /etc/default/nfs file, see nfs(1M).
The setoncenv command initializes, displays, and removes the value of NFS configuration
variables found in either of the following files:
• /etc/rc.config.d/nfsconf
• /etc/rc.config.d/namesvrs
• /etc/default/autofs
• /etc/default/keyserv
• /etc/default/nfs
• /etc/default/nfslogd
• /etc/pcnfsd.conf
For more information on the setoncenv command, see setoncenv(1M).
Configuring and Using NFS Netgroups
This section describes how to create and use NFS netgroups to restrict NFS access to your system.
It describes the following tasks:
• “Creating Netgroups in the /etc/netgroup File” (page 41)
• “Using Netgroups in Configuration Files” (page 43)
Creating Netgroups in the /etc/netgroup File
To create netgroups in the /etc/netgroup file, follow these steps:
1. If you are using the local /etc/netgroup file or the NIS netgroup map for netgroups,
add entries with the following syntax to the /etc/netgroup file.
netgroup_name (host, user, NIS_domain) (host, user, NIS_domain) ...
If you are using NIS, edit the /etc/netgroup file only on the NIS master server.
2. If you are using NIS to manage your netgroups database, enter the following commands
on the NIS master server to generate the netgroup, netgroup.byhost, and
netgroup.byuser maps from the /etc/netgroup file, and push the generated maps to
the NIS slave servers:
cd /var/yp
/usr/ccs/bin/make netgroup
A netgroup can be used in most NFS and NIS configuration files, instead of a host name or a user
name. A netgroup does not create a relationship between users and hosts. When a netgroup is
used in a configuration file, it represents either a group of hosts or a group of users, but never
both.
If you are using BIND (DNS) for hostname resolution, hosts must be specified as fully qualified
domain names, for example: turtle.bio.nmt.edu.
If host, user, or NIS_domain is left blank in a netgroup, that field can take any value. If a dash
(-) is specified in any field of a netgroup, that field can take no value.
Configuring and Using NFS Netgroups 41