From: Matt Bernstein <mb/lkml@dcs.qmul.ac.uk>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6: can't lockf() over NFS
Date: Wed, 26 Nov 2003 11:21:33 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.58.0311261120220.22074@localhost.localdomain> (raw)
In-Reply-To: <20031125165501.A20302@build.pdx.osdl.net>
On Nov 25 Chris Wright wrote:
>> I tried writing a trivial program to test lockf() and it returns ENOLCK
>> over NFS, but succeeds locally. The client kernel offers some grumbles:
>>
>> RPC: Can't bind to reserved port (13).
>> RPC: can't bind to reserved port.
>> nsm_mon_unmon: rpc failed, status=-5
>> lockd: cannot monitor a.b.c.d
>> lockd: failed to monitor a.b.c.d
>Yes, can you either change your config to:
>
>CONFIG_SECURITY=n
>
>or:
>
>CONFIG_SECURITY=y
>CONFIG_SECURITY_CAPABILITIES=y
>
>or:
>
>CONFIG_SECURITY=y
>CONFIG_SECURITY_CAPABILITIES=m
>and modprobe capability
>
>Thanks, this had fallen off my radar.
Thank you, problem solved :)
prev parent reply other threads:[~2003-11-26 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 16:17 2.6: can't lockf() over NFS Matt Bernstein
2003-11-26 0:39 ` Trond Myklebust
2003-11-26 0:55 ` Chris Wright
2003-11-26 1:35 ` Trond Myklebust
2003-11-26 11:21 ` Matt Bernstein [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=Pine.LNX.4.58.0311261120220.22074@localhost.localdomain \
--to=mb/lkml@dcs.qmul.ac.uk \
--cc=chrisw@osdl.org \
--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;
as well as URLs for NNTP newsgroup(s).