nfsiod(8) [osx man page]

NFSIOD(8)						    BSD System Manager's Manual 						 NFSIOD(8)

NAME

     nfsiod -- local NFS asynchronous I/O

SYNOPSIS

     nfsiod [-n num_threads]

DESCRIPTION

     nfsiod is deprecated.  See nfs.conf(5) for NFS configuration info.

     nfsiod controls the maximum number of asynchronous I/O threads used for NFS mounts.  Historically, it has consisted of a daemon that never
     exits.  However, asynchronous I/O requests are now serviced by threads launched on demand in the kernel and the nfsiod command simply sets
     the configuration limit.

     Having asynchronous I/O threads improves performance but is not required for correct operation.

     The options are as follows:

     -n      Specify maximum number of asynchronous I/O threads to be used.

     If no maximum is specified, nfsiod displays the current value.  The default value is 16.  A client should allow enough threads to handle its
     maximum level of concurrency.

     The nfsiod utility exits 0 on success, and >0 if an error occurs.

SEE ALSO

     nfs.conf(5), mount_nfs(8), nfsstat(1)

HISTORY

     The nfsiod utility first appeared in 4.4BSD.  It's use was deprecated in Darwin 9.

BSD
								 October 25, 2006							       BSD

NFSIOD(8)						    BSD System Manager's Manual 						 NFSIOD(8)

NAME

     nfsiod -- local NFS asynchronous I/O server

SYNOPSIS

     nfsiod [-n num_servers]

DESCRIPTION

     The nfsiod utility controls the maximum number of nfsiod kernel processes which run on an NFS client machine to service asynchronous I/O
     requests to its server.  Having nfsiod kernel processes improves performance but is not required for correct operation.

     The option is as follows:

     -n      Specify how many processes are permitted to be started.

     Without an option, nfsiod displays the current settings.  A client should allow enough number of processes to handle its maximum level of
     concurrency, typically four to six.

     If nfsiod detects that the running kernel does not include NFS support, it will attempt to load a kernel module containing NFS code, using
     kldload(2).  If this fails, or no NFS module was available, nfsiod exits with an error.

EXIT STATUS

     The nfsiod utility exits 0 on success, and >0 if an error occurs.

SEE ALSO

     nfsstat(1), kldload(2), nfssvc(2), mountd(8), nfsd(8), rpcbind(8)

HISTORY

     The nfsiod utility first appeared in 4.4BSD.

     Starting with FreeBSD 5.0, the utility no longer starts daemons, but only serves as a vfs loader and sysctl(3) wrapper.

BSD
								 December 26, 2009							       BSD