From owner-freebsd-current Fri Nov 22 10:56:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23AD837B401; Fri, 22 Nov 2002 10:56:15 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC47843EB7; Fri, 22 Nov 2002 10:56:13 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id gAMIuABF069033; Fri, 22 Nov 2002 13:56:10 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 22 Nov 2002 13:56:09 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: John Baldwin Cc: "local.freebsd.current" , "freebsd-current@freebsd.org" Subject: RE: DP2: nfsiod In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Nov 2002, John Baldwin wrote: > On 22-Nov-2002 local.freebsd.current wrote: > > Having installed DP2 and said NO to NFS client and > > server in sysinstall (and there's nothing about them > > in /etc/rc.conf) I see four nfsiod daemons running > > after the first boot. Are they supposed to be there? > > Yes. If you have NFS client support in your kernel they will be there. > GENERIC has NFS client support enabled by default. Hmm this is kind of > a policy change as it now means that nfs_client_enable is basically > useless unless you compile a custom kernel w/o NFS client support in > which case the startup scripts will attempt to load it as a module for > you. Per our phone conversation this morning, the way to think about it is this: The only function of nfsiod is to provide asynchronous write-behind functionality. On -STABLE, even if nfsiod isn't actually running, if the NFS client code is present in the kernel, NFS will still work. What nfs_client_enable should do is: (1) Load the kernel module if it's not already loaded (2) Tune the kernel module if appropriate (3) Possibly start rpcbind as a dependency (4) Possibly start rpc.statd as a dependency (5) Possibly start rpc.lockd as a dependency Note that the rpc.lockd support is still experimental in 5.0 for client-side locking, and as such, might not be good to enable by default. I notice that in the original message for this thread, there's reference to release documentation indicating that client side locking isn't implemented: this is actually not the case. We do implement it now. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message