From owner-freebsd-questions@FreeBSD.ORG Fri Mar 16 16:21:23 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F61816A407 for ; Fri, 16 Mar 2007 16:21:23 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id C35FF13C4BA for ; Fri, 16 Mar 2007 16:21:12 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan@localhost [127.0.0.1]) by dan.emsphone.com (8.14.0/8.13.8) with ESMTP id l2GGL6Ds029523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 16 Mar 2007 11:21:06 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.0/8.14.0/Submit) id l2GGL6hJ029522; Fri, 16 Mar 2007 11:21:06 -0500 (CDT) (envelope-from dan) Date: Fri, 16 Mar 2007 11:21:06 -0500 From: Dan Nelson To: Konrad Heuer Message-ID: <20070316162106.GA64778@dan.emsphone.com> References: <20070316161325.C62317@gwdu60.gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070316161325.C62317@gwdu60.gwdg.de> X-OS: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-questions@freebsd.org Subject: Re: nfsiod && nfs_client_flags X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2007 16:21:23 -0000 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