Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Mar 2007 11:21:06 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Konrad Heuer <kheuer2@gwdg.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: nfsiod && nfs_client_flags
Message-ID:  <20070316162106.GA64778@dan.emsphone.com>
In-Reply-To: <20070316161325.C62317@gwdu60.gwdg.de>
References:  <20070316161325.C62317@gwdu60.gwdg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Mar 16), Konrad Heuer said:
> after replacing 4.11-RELEASE by 6.1-RELEASE on most of my systems I
> just remembered the rc.conf variable "nfs_client_flags" which I used
> under 4.x to raise the number of nfsiod's on heavily loaded systems.
> I can't find nfs_client_flags in 6.1 although the man page of nfsiod
> still documents the "-n" flag.

nfsiods in 5.* and newer are completely kernel-based and are controlled
by three sysctls: vfs.nfs.iodmin, vfs.nfs.iodmax, and
vfs.nfs.iodmaxidle.  The kernel will automatically start up new nfsiods
as it needs them, up to 'iodmax'.  If an nfsiod had been idle for
'iodmaxidle' seconds, the kernel will kill it off, but will always
leave at least 'iodmin' processes running.

All /sbin/nfsiod does is set the iodmax sysctl (which defaults to 20);
it's not really needed anymore.

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070316162106.GA64778>