nfsd(1m) [hpux man page]
nfsd(1M) nfsd(1M) NAME
nfsd - NFS daemon SYNOPSIS
#_conn] listen_backlog] protocol] device] [nservers] DESCRIPTION
is the daemon that handles client file system requests. Only users with sufficient privileges can run this daemon. The daemon is automatically invoked if and in the file. By default, starts over the TCP and UDP transports for version 2 and version 3, and over TCP for version 4, if NFS version 4 is enabled. One can change this with the option. A previously invoked daemon started with or without options must be stopped before invoking another command. Administrators wanting to change startup parameters for should make changes (as root user) to the NFS default file (see nfs(4)). Adminis- trators can either edit this file or use the command to make changes. Options The following options are supported: Start a NFS daemon over all available connectionless and connection-oriented transports, including UDP and TCP. Equivalent to set- ting the parameter to in the NFS default file. This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the number of connections is unlimited. Equivalent to the parameter in the NFS default file. Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries. Equivalent to the parameter in the NFS default file. Start a NFS daemon over the specified protocol. Equivalent to the parameter in the NFS default file. Start a NFS daemon for the transport specified by the given device. Equivalent to the parameter in the NFS default file. Operands The following operands are supported: 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. 16 is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1. Changing the value of nservers requires stopping and restarting Equivalent to the parameter in the NFS default file. Notes A directory service that provides service name data base support must have the following service entries in its database: If the kernel tunable (see nfs_portmon(5)) is set to 1, then clients are required to use privileged ports (ports < IPPORT_RESERVED) to receive NFS services. This tunable is set to 0 by default. Use (see kctune(1M)) to set this tunable. By default, the NFS version 4 server is disabled. In order to enable it you must stop the NFS server. As root, either use the command (see setoncenv(1M)) or edit to set the parameter to 4. EXIT STATUS
Daemon started successfully. Daemon failed to start. WARNINGS
Manually starting and restarting is not recommended. If it is necessary to do so, use the NFS server start/stop script FILES
client machine pointer to an open-but-unlinked file. shell script for starting startup parameters for directories used by the server to manage client state information; these directories should not be removed. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
kctune(1M), mountd(1M), setoncenv(1M), getservent(3N), nfs(4), nsswitch.conf(4), services(4), sharetab(4), nfs_portmon(5). nfsd(1M)
Check Out this Related Man Page
nfsd(1M) nfsd(1M) NAME
nfsd - NFS daemon SYNOPSIS
/usr/lib/nfs/nfsd [-a] [-c #_conn] [-l listen_backlog] [-p protocol] [-t device] [nservers] nfsd is the daemon that handles client file system requests. Only users with {PRIV_SYS_NFS} and sufficient privileges to write to /var/run can run this daemon. The nfsd daemon is automatically invoked using share(1M) with the -a option. By default, nfsd starts over the TCP and UDP transports for versions 2 and 3. By default, it starts over the TCP for version 4. You can change this with the -p option. A previously invoked nfsd daemon started with or without options must be stopped before invoking another nfsd command. Administrators wanting to change startup parameters for nfsd should, as root, make changes in the /etc/default/nfs file. See nfs(4). The following options are supported: -a Start a NFS daemon over all available connectionless and connection-oriented transports, including UDP and TCP. Equivalent of setting the NFSD_PROTOCOL parameter to ALL in the nfs file. -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. Equivalent of the NFSD_MAX_CONNECTIONS parameter in the nfs file. -l Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries. Equiva- lent of the NFSD_LISTEN_BACKLOG parameter in the nfs file. -p protocol Start a NFS daemon over the specified protocol. Equivalent of the NFSD_PROTOCOL parameter in the nfs file. -t device Start a NFS daemon for the transport specified by the given device. Equivalent of the NFSD_DEVICE parameter in the nfs file. The following operands are supported: 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. 16 is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1. Equivalent of the NFSD_SERVERS parameter in the nfs file. USAGE
If the NFS_PORTMON variable is set in /etc/system, then clients are required to use privileged ports (ports < IPPORT_RESERVED) 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 0 Daemon started successfully. 1 Daemon failed to start. .nfsXXX Client machine pointer to an open-but-unlinked file. /etc/default/nfs Contains startup parameters for nfsd. /etc/system System configuration information file. /var/nfs/v4_state Directories used by the server to manage client state information. These directories should not be removed. /var/nfs/v4_oldstate See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfssu | +-----------------------------+-----------------------------+ ps(1), svcs(1), mountd(1M), share(1M), svcadm(1M), nfs(4), sharetab(4), system(4), attributes(5), smf(5) 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 Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If nfsd is killed with SIGTERM, it will not be restarted by the service management facility. Instead, nfsd can be restarted by other sig- nals, such as SIGINT. 27 Apr 2005 nfsd(1M)