From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: <linux-kernel@vger.kernel.org>, apark@cdf.toronto.edu
Subject: Re: 2.2.19 and file lock on NFS?
Date: Thu, 26 Apr 2001 02:53:56 -0700 [thread overview]
Message-ID: <200104260953.f3Q9rui03376@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <shsvgntkjm8.fsf@charged.uio.no>
On 25 Apr 2001 00:39:43 +0200, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>>>>>> " " == apark <apark@cdf.toronto.edu> writes:
>
> > Hi, Recently upgraded to 2.2.19, along with new
> > nfs-utils(0.3.1). But I have a program that requires a
> > exclusive write lock on a NFSed directory. When I was using
> > 2.2.17 all was ok, but now it returns ENOLCK. Does anybody
> > else have the same problem? Thanks
>
> Hi,
>
> You are probably failing to run the statd daemon or you may have set
> up over-restrictive /etc/hosts.(allow|deny).
Or /var/lib/nfs/statd does not exist on your system, or it is not
writable by the uid rpc.statd runs under (rpcuser on Red Hat boxes
with all the upgrades).
I've had this problem myself, I don't think it's covered in the FAQ.
I haven't checked if the rpcuser thing is a redhat-ism, probably is,
their script is not doing anything special with rpc.statd so they
must have hacked it into the executable.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
prev parent reply other threads:[~2001-04-26 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 20:38 2.2.19 and file lock on NFS? apark
2001-04-24 22:39 ` Trond Myklebust
2001-04-26 9:53 ` Ion Badulescu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200104260953.f3Q9rui03376@moisil.dev.hydraweb.com \
--to=ionut@moisil.cs.columbia.edu \
--cc=apark@cdf.toronto.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox