From owner-freebsd-current@FreeBSD.ORG Mon Jun 25 02:33:44 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB2CA16A400 for ; Mon, 25 Jun 2007 02:33:44 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 71E6013C448 for ; Mon, 25 Jun 2007 02:33:44 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.61]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l5P2XfhL098774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Jun 2007 12:03:42 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Mon, 25 Jun 2007 12:03:32 +0930 User-Agent: KMail/1.9.5 References: <20070622210119.GA4186@clamps.exit2shell.com> <467F12FA.8070406@delphij.net> <20070625.105539.-1300543753.ken@tydfam.jp> In-Reply-To: <20070625.105539.-1300543753.ken@tydfam.jp> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1723602.7yHBIdeoUh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200706251203.39543.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Subject: Re: Q) lockf(flock?) on -current (amd64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 02:33:44 -0000 --nextPart1723602.7yHBIdeoUh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 25 June 2007 11:25, Ken Yamada wrote: > I noticed that lockf(flock) does not function as expected for any > files on NFS file system with -current. ( I cannnot create workspace > on NFS filesystem with eclipse because of this.) > > Is this an intended functionality or a bug? If you're not running rpc.lockd then it is expected :) I have a -current NFS client talking to a 6.2 server using rpc.lockd and=20 it works as expected (openoffice is happy) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1723602.7yHBIdeoUh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBGfymD5ZPcIHs/zowRAsWwAKCRGKBu2uJ63iqxZ7Oqe/0G/ANzGgCfVP0Q ONpFw8funbPe2emD5nz2bzk= =Ec9F -----END PGP SIGNATURE----- --nextPart1723602.7yHBIdeoUh--