From owner-freebsd-questions@FreeBSD.ORG Fri Jan 14 03:26:26 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F72216A4CE for ; Fri, 14 Jan 2005 03:26:26 +0000 (GMT) Received: from ecserv7.uwaterloo.ca (ecserv7.uwaterloo.ca [129.97.50.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03C4D43D2F for ; Fri, 14 Jan 2005 03:26:26 +0000 (GMT) (envelope-from bruce@engmail.uwaterloo.ca) Received: from ecserv7.uwaterloo.ca (localhost.uwaterloo.ca [127.0.0.1]) j0E3QVAG009587; Thu, 13 Jan 2005 22:26:31 -0500 (EST) (envelope-from bruce@engmail.uwaterloo.ca) Received: (from www@localhost) by ecserv7.uwaterloo.ca (8.12.10/8.12.10/Submit) id j0E3QUqm009586; Thu, 13 Jan 2005 22:26:30 -0500 (EST) (envelope-from bruce@engmail.uwaterloo.ca) X-Authentication-Warning: ecserv7.uwaterloo.ca: www set sender to bruce@engmail.uwaterloo.ca using -f Received: from 65.93.198.45 ( [65.93.198.45])HTTP; Thu, 13 Jan 2005 22:26:30 -0500 Message-ID: <1105673190.41e73be6d7349@www.nexusmail.uwaterloo.ca> Date: Thu, 13 Jan 2005 22:26:30 -0500 From: Bruce Campbell To: freebsd-questions@freebsd.org References: <1105670575.41e731af8de9a@www.nexusmail.uwaterloo.ca> <20050114024656.GA66730@xor.obsecurity.org> In-Reply-To: <20050114024656.GA66730@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 / FreeBSD-4.6.2 X-Originating-IP: 65.93.198.45 cc: Paul McKone Subject: Re: flock failure on NFS from 5.3 client to 4.7 server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 03:26:26 -0000 Quoting Kris Kennaway : > > ... > > After the mail server upgrade to 5.3, flock gives error "operation not supported" > > on nfs mounted home directories. > > ... > > On our NFS server, rpc.statd is running, but rpc.lockd wasn't. Started > > it, still no worky. Killed it, other 4.7 clients still flock fine. > > rpc.lockd needs to be running on *both* client *and* server. > > 4.x gets away with it because the rpc.lockd implementation does not in > fact implement locking on the client. > > Kris > Thanks, that has fixed it, and I've added the appropriate rc.conf settings on the client: rpc_lockd_enable="YES" # Run NFS rpc.lockd needed for client/serv rpc_statd_enable="YES" # Run NFS rpc.statd needed for client/serv rpcbind_enable="YES" # Run the portmapper service and on the server: rpc_lockd_enable="YES" # Run NFS rpc.lockd (*broken!*) if nfs_server. rpc_statd_enable="YES" # Run NFS rpc.statd if nfs_server (or NO). -- Bruce Campbell Engineering Computing CPH-2374B University of Waterloo (519)888-4567 ext 5889 ---------------------------------------- This mail sent through www.mywaterloo.ca