From owner-freebsd-current  Tue Mar 18 19: 5: 8 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 E114F37B401
	for <current@freebsd.org>; Tue, 18 Mar 2003 19:05:06 -0800 (PST)
Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4399543F75
	for <current@freebsd.org>; Tue, 18 Mar 2003 19:05:06 -0800 (PST)
	(envelope-from tlambert2@mindspring.com)
Received: from pool0067.cvx40-bradley.dialup.earthlink.net ([216.244.42.67] helo=mindspring.com)
	by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)
	id 18vTt1-0004ex-00; Tue, 18 Mar 2003 19:05:04 -0800
Message-ID: <3E77DE13.11BA7743@mindspring.com>
Date: Tue, 18 Mar 2003 19:03:47 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Andrew P. Lentvorski, Jr." <bsder@allcaps.org>
Cc: Steve Sizemore <steve@ls.berkeley.edu>, current@freebsd.org
Subject: Re: NFS file unlocking problem
References: <Pine.LNX.4.44.0303181722440.21978-100000@mail.allcaps.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f17451f0550644b9c102807a4983bf41667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

"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.

I thought this was a fork on purpose, and the second one was there
for LOCK vs. LOCKW requests?

If not, how the heck is he starting this in the first place?!?

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message