Date: Mon, 25 Jun 2007 12:03:32 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-current@freebsd.org Subject: Re: Q) lockf(flock?) on -current (amd64) Message-ID: <200706251203.39543.doconnor@gsoft.com.au> In-Reply-To: <20070625.105539.-1300543753.ken@tydfam.jp> References: <20070622210119.GA4186@clamps.exit2shell.com> <467F12FA.8070406@delphij.net> <20070625.105539.-1300543753.ken@tydfam.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706251203.39543.doconnor>