public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.2.19 and file lock on NFS?
@ 2001-04-24 20:38 apark
  2001-04-24 22:39 ` Trond Myklebust
  0 siblings, 1 reply; 3+ messages in thread
From: apark @ 2001-04-24 20:38 UTC (permalink / raw)
  To: linux-kernel

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

-Andrew


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.2.19 and file lock on NFS?
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Trond Myklebust @ 2001-04-24 22:39 UTC (permalink / raw)
  To: apark; +Cc: linux-kernel

>>>>> " " == 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.2.19 and file lock on NFS?
  2001-04-24 22:39 ` Trond Myklebust
@ 2001-04-26  9:53   ` Ion Badulescu
  0 siblings, 0 replies; 3+ messages in thread
From: Ion Badulescu @ 2001-04-26  9:53 UTC (permalink / raw)
  To: Trond Myklebust; +Cc: linux-kernel, apark

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-04-26  9:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox