nfsd is the daemon that handles client filesystem requests. The command must have the
privilege to run effectively.
The nfsd daemon is automatically invoked in run level 3 with the -a option.
By default nfsd will start over the TCP and UDP transports.
A previously invoked nfsd daemon started with or without options must be stopped before invoking another nfsd command.
The following options are supported:
Start a NFS daemon over all available connectionless and connection-oriented transports, including TCP and UDP.
This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the number of connections is unlimited.
Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries.
Start a NFS daemon over the specified protocol.
Start a NFS daemon for the transport specified by the given device.
The following operands are supported:
Set the maximum number of concurrent NFS requests that the server can handle. This concurrency is achieved by up to nservers threads created as needed in the kernel. nservers should be based on the load expected on this server. 16 is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1.
If the NFS_PORTMON variable is set, then clients are required to use privileged ports (ports < IPPORT_RESERVED) in order to get NFS services. In the Trusted Solaris environment, this variable is set to 1 by default. This variable has been moved from the "nfs" module to the "nfssrv" module. To set the variable, edit the /etc/system file and add this entry:
set nfssrv:nfs_portmon = 1
Client machine pointer to an open-but-unlinked file
Shell script for starting nfsd
System configuration information file
See attributes(5) for descriptions of the following attributes:
|ATTRIBUTE TYPE||ATTRIBUTE VALUE|
net_mac_read privileges are required to run this daemon. NFS_PORTMON has been set to 1 by default.
The NFS service uses kernel threads to process all of the NFS requests. Currently, system utilization associated with these threads is not charged to the nfsd process. Therefore, ps(1) can report 0 cpu time associated with the NFS daemon, even though NFS processing is taking place on the server.
Manually starting and restarting nfsd is not recommended. If it is necessary to do so, use the NFS server start/stop script (/etc/init.d/nfs.server). See System Administration Guide, Volume 3 for more information.