nfsd(1M)
NAME
nfsd − NFS daemon
SYNOPSIS
nfsd [ −a ] [ −p protocol ] [ −t device ] [ −c #_conn ] [ nservers ]
DESCRIPTION
nfsd is the daemon that handles client file system requests. Only the super-user can run this daemon.
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.
OPTIONS
−a Start a NFS daemon over all available connectionless and connection-oriented transports, including udp and tcp.
−p protocol Start a NFS daemon over the specified protocol.
−t device Start a NFS daemon for the transport specified by the given device.
−c #_conn This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the number of connections is unlimited.
nservers This sets 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. Sixteen is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to one.
If the NFS_PORTMON variable is set, then clients are required to use privileged ports (ports < IPPORT_RESERVED) in order to get NFS services. This variable is equal to zero 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
FILES
.nfsXXX client machine pointer to an open-but-unlinked file
SEE ALSO
ps(1), mountd(1M), sharetab(4)
BUGS
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.
SunOS 5.5/x86 — Last change: 20 Apr 1995