From owner-freebsd-net@FreeBSD.ORG  Thu Jan 11 20:07:42 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8D38616A407
	for <freebsd-net@freebsd.org>; Thu, 11 Jan 2007 20:07:42 +0000 (UTC)
	(envelope-from vanhu@zeninc.net)
Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25])
	by mx1.freebsd.org (Postfix) with ESMTP id 5386813C467
	for <freebsd-net@freebsd.org>; Thu, 11 Jan 2007 20:07:41 +0000 (UTC)
	(envelope-from vanhu@zeninc.net)
Received: by smtp.zeninc.net (smtpd, from userid 1000)
	id 1958B3F17; Thu, 11 Jan 2007 21:07:41 +0100 (CET)
Date: Thu, 11 Jan 2007 21:07:41 +0100
From: VANHULLEBUS Yvan <vanhu_bsd@zeninc.net>
To: freebsd-net@freebsd.org
Message-ID: <20070111200740.GB6884@zen.inc>
References: <20070111161754.GA955@zen.inc> <45A66609.4090307@delphij.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45A66609.4090307@delphij.net>
User-Agent: All mail clients suck. This one just sucks less.
Subject: Re:  NFS locking broken
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2007 20:07:42 -0000

On Fri, Jan 12, 2007 at 12:30:01AM +0800, LI Xin wrote:

Thanks for the fast reply !

> Sounds like an known and fixed issue.  Try this patch:
> 
> http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/rpc.lockd/lockd_lock.c.diff?r1=1.18&r2=1.19

Just tried it, and I still have the problem.

The really strange thing is that one "thing" (an application from
/usr/local ???) blocks ALL the NFS locking system, for all users and
all process...

And as I also have the problem if I just reboot the computer then make
a test on console or ssh (no X server, no applications, etc...), the
only programs from /usr/ports which have been run at that point are
cups (which doesn't use the NFS /home AFAIK), bash and pam_ldap.

And I just tried again: stopping/restarting nfslocking doesn't change
anything (tried a lockf just after restarting nfslock).



Yvan.

-- 
NETASQ
http://www.netasq.com