From owner-freebsd-stable@FreeBSD.ORG Thu Dec 1 15:50:05 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88A7F16A41F for ; Thu, 1 Dec 2005 15:50:05 +0000 (GMT) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay3.uni-hannover.de (mrelay3.uni-hannover.de [130.75.2.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id D591343D46 for ; Thu, 1 Dec 2005 15:50:04 +0000 (GMT) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay3.uni-hannover.de (8.12.10/8.12.10) with ESMTP id jB1Fo0J3009724 for ; Thu, 1 Dec 2005 16:50:01 +0100 (MET) Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 0B899D4 for ; Thu, 1 Dec 2005 16:49:56 +0100 (CET) Date: Thu, 1 Dec 2005 16:49:55 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-stable@freebsd.org Message-Id: <20051201164955.788ba69e.gerrit@pmp.uni-hannover.de> Organization: Plasmaphysik X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (mrelay3.uni-hannover.de [130.75.2.41]); Thu, 01 Dec 2005 16:50:01 +0100 (MET) X-Scanned-By: MIMEDefang 2.42 Subject: nfs locking (was: Re: OOO 2.0 compiles but doesn't work properly) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 15:50:05 -0000 On Wed, 30 Nov 2005 10:29:02 -0500 Robert Huff wrote about OOO 2.0 compiles but doesn't work properly: RH> > The home directory is coming from a nfs-server, so the user-setup RH> > should be identical. I already tried to delete .openoffice.org2, RH> > but that didn't help either. Any further hints? RH> Yes - check the archives. There was at least one other person RH> reporting problems with OpenOffice+NFS. Yes, I see... the problem seems so be that you have to run lockd and statd to get ooo running on nfs. The machine where everything's working fine is running 5.4 with statd and lockd. The machine with the problems is running 6.0 and didn't have statd and lockd activated. However, activating them (and rebooting) didn't solve the problem here. That's why I'm taking this over to -stable mailing list: I've got a FreeBSD 6.0 NFS client here, which is connected to a FreeBSD 4.10-Server. Both sides are running statd and lockd, but processes requesting locks (kdm in the first place after booting here) get stuck in the state "lockd". The same setup works fine with a FreeBSD 5.4 client. Are there any known problems concerning nfs and 6.0, or do I miss anything else? cu Gerrit