From owner-freebsd-arch@FreeBSD.ORG Mon Jun 26 09:47:06 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E7E716A405 for ; Mon, 26 Jun 2006 09:47:06 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CC443D7F for ; Mon, 26 Jun 2006 09:46:58 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout1.pacific.net.au (Postfix) with ESMTP id BE976329642; Mon, 26 Jun 2006 19:46:56 +1000 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k5Q9kruP004707; Mon, 26 Jun 2006 19:46:54 +1000 Date: Mon, 26 Jun 2006 19:46:53 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Andrew Reilly In-Reply-To: <20060626181131.G67741@delplex.bde.org> Message-ID: <20060626194341.I67977@delplex.bde.org> References: <20060625011746.GC81052@duncan.reilly.home> <20060625013110.GA62237@troutmask.apl.washington.edu> <20060625020154.GA89358@gurney.reilly.home> <20060626002658.A65226@delplex.bde.org> <20060625213605.GA93766@duncan.reilly.home> <20060626181131.G67741@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Steve Kargl , freebsd-arch@FreeBSD.org Subject: Re: What's up with our stdout? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2006 09:47:06 -0000 On Mon, 26 Jun 2006, I wrote: > Configuring of locking for nfs is confusing and poorly documented. > Neither rpc.lockd nor rpc.statd gets started automatically when a file > system is nfs-mounted without nolockd. This wouldn't be easy to > automate, since the daemons must be started on both the clients and > servers. mount_nfs(8) doesn't say clearly which daemons must be started > where. rc.conf(5) says wrongly that rpc_lock_lockd and rpc_statd_enable > only apply to servers. Starting them both on clients and servers seems > to be needed. With a filesystem nfs-remounted without nolockd: there > seem to be ordering or timing requirements for starting them -- starting > them manually sometimes gave a useful error message for flock() attempts > when not all were started, but sometimes starting them all didn't stop > flock() from failing and other times gave a hung flock(). Killing and > restarting rpc.lockd on the client (while leaving the other daemons > running) usually worked to unhang flock() and make it work on the next > try. I didn't actually find a usable configuration of nfs locking, since the above left rpc.lockd taking 100% CPU on both the client and server. This was with FreeBSD-~5.2. Some of the many bugs in rpc.lockd have been fixed since 5.2. Bruce