From owner-freebsd-current Tue Mar 18 21: 4:36 2003 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 AF2E737B401 for ; Tue, 18 Mar 2003 21:04:34 -0800 (PST) Received: from Math.Berkeley.EDU (gold.Math.Berkeley.EDU [169.229.58.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF5F043F85 for ; Tue, 18 Mar 2003 21:04:31 -0800 (PST) (envelope-from steve@Math.Berkeley.EDU) Received: from bootjack.math.berkeley.edu (root@bootjack.Math.Berkeley.EDU [169.229.58.46]) by Math.Berkeley.EDU (8.12.8/8.12.8) with ESMTP id h2J54UeB012619; Tue, 18 Mar 2003 21:04:30 -0800 (PST) Received: from bootjack.math.berkeley.edu (steve@localhost [127.0.0.1]) by bootjack.math.berkeley.edu (8.12.6/8.12.6) with ESMTP id h2J54PUu001340; Tue, 18 Mar 2003 21:04:25 -0800 (PST) (envelope-from steve@bootjack.math.berkeley.edu) Received: (from steve@localhost) by bootjack.math.berkeley.edu (8.12.6/8.12.6/Submit) id h2J54Px1001339; Tue, 18 Mar 2003 21:04:25 -0800 (PST) (envelope-from steve) Date: Tue, 18 Mar 2003 21:04:25 -0800 From: Steve Sizemore To: "Andrew P. Lentvorski, Jr." Cc: Terry Lambert , current@freebsd.org Subject: Re: NFS file unlocking problem Message-ID: <20030319050424.GA1322@math.berkeley.edu> Reply-To: Steve Sizemore References: <20030318172237.GA320@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i 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 Tue, Mar 18, 2003 at 05:25:36PM -0800, Andrew P. Lentvorski, Jr. wrote: > On Tue, 18 Mar 2003, Steve Sizemore wrote: > > > root 399 0.0 0.1 263496 1000 ?? Is 9:11AM 0:00.00 /usr/sbin/rpc.sta > > root 402 0.0 0.1 1512 1156 ?? Ss 9:11AM 0:00.00 /usr/sbin/rpc.loc > > daemon 405 0.0 0.1 1484 1176 ?? I 9:11AM 0:00.00 /usr/sbin/rpc.loc > > This might be the culprit. The way that rpc.lock works is that it grabs a > lock on the *entire* underlying file when any lock request comes in. If > those requests get misrouted to the wrong daemon, it is likely to cause > havoc. > OK. It appears that starting rpc.lockd automatically spawns two copies, so if that's a problem, how can I fix it? Thanks. Steve -- Steve Sizemore , (510) 642-8570 Unix System Manager Dept. of Mathematics and College of Letters and Science University of California, Berkeley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message