From owner-freebsd-current@FreeBSD.ORG Mon Aug 1 16:31:49 2005 Return-Path: X-Original-To: current@freebsd.org 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 5158616A41F for ; Mon, 1 Aug 2005 16:31:49 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF1F43D48 for ; Mon, 1 Aug 2005 16:31:48 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.4/8.13.4) with ESMTP id j71GViRw001825; Mon, 1 Aug 2005 09:31:45 -0700 (PDT) (envelope-from marcel@xcllnt.net) In-Reply-To: <86ll3lrdka.fsf@xps.des.no> References: <560747f4f3d58887485e1a2c0c25ac26@xcllnt.net> <86ll3lrdka.fsf@xps.des.no> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <9dd42c075d8542dc6695ce1077b96162@xcllnt.net> Content-Transfer-Encoding: quoted-printable From: Marcel Moolenaar Date: Mon, 1 Aug 2005 09:31:44 -0700 To: des@des.no (=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=) X-Mailer: Apple Mail (2.622) Cc: current@freebsd.org Subject: Re: 6.0-BETA1: rpc.lockd broken for NFS server only configuration X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2005 16:31:49 -0000 On Aug 1, 2005, at 6:28 AM, Dag-Erling Sm=F8rgrav wrote: >> I could of course add nfsclient to my kernel configuration file, but >> that annihilates the effort to split the server functionality from >> the client functionality, so that's no solution. > > No. A server needs both nfsserver and nfsclient, but a client needs > only nfsclient. This is a change from 5.x and 4.x, then. I never needed nfsclient on my server before. Why then do I need nfsclient now, ignoring for a moment that the nfslock pseudo-device is only present for nfsclient as that is what I think is broken? --=20 Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net