From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: <apark@cdf.toronto.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.19 and file lock on NFS?
Date: 25 Apr 2001 00:39:43 +0200 [thread overview]
Message-ID: <shsvgntkjm8.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0104241633490.19976-100000@penguin.cdf.toronto.edu>
In-Reply-To: <apark@cdf.toronto.edu>'s message of "Tue, 24 Apr 2001 16:38:10 -0400 (EDT)"
>>>>> " " == 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).
See the latest NFS-HOWTO for a full description on how to set up
locking.
Cheers,
Trond
next prev parent reply other threads:[~2001-04-24 22:40 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 [this message]
2001-04-26 9:53 ` Ion Badulescu
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=shsvgntkjm8.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=apark@cdf.toronto.edu \
--cc=linux-kernel@vger.kernel.org \
/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