Date: Mon, 24 Nov 2008 15:40:07 GMT From: "Remko Lodder" <remko@elvandar.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/129132: 7.1-Beta2 nfsd cannot lock Message-ID: <200811241540.mAOFe7PE036424@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/129132; it has been noted by GNATS.
From: "Remko Lodder" <remko@elvandar.org>
To: "Clarence CHU" <clcchu@hotmail.com>
Cc: freebsd-gnats-submit@freebsd.org,
dfr@FreeBSD.org
Subject: Re: kern/129132: 7.1-Beta2 nfsd cannot lock
Date: Mon, 24 Nov 2008 15:59:31 +0100 (CET)
On Mon, November 24, 2008 2:27 pm, Clarence CHU wrote:
For clarity's sake:
I assume you read the manual page and noticed this;
-L Do not forward fcntl(2) locks over the wire. All locks will be
local and not seen by the server and likewise not seen by other
NFS clients. This removes the need to run the rpcbind(8)
service
and the rpc.statd(8) and rpc.lockd(8) servers on the client.
Note that this option will only be honored when performing the
initial mount, it will be silently ignored if used while
updating
the mount options.
Which results in the question: do you have rpc.statd and rpc.lockd running
on the machine?
I copied in Doug Rabson, who did a lot of work on NFS recently and might
have more information wrt. Locking etc. (or not, then I was mistaken).
thanks for sending the info and taking the time to report this! It's
appreciated!
--
/"\ Best regards, | remko@FreeBSD.org
\ / Remko Lodder | remko@EFnet
X http://www.evilcoder.org/ |
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811241540.mAOFe7PE036424>