* 2.6: can't lockf() over NFS
@ 2003-11-25 16:17 Matt Bernstein
2003-11-26 0:39 ` Trond Myklebust
2003-11-26 0:55 ` Chris Wright
0 siblings, 2 replies; 5+ messages in thread
From: Matt Bernstein @ 2003-11-25 16:17 UTC (permalink / raw)
To: linux-kernel
I can't get Debian testing to log in to GNOME when home directories are
mounted over NFS (Linux 2.6 client -> Linux 2.4-ac server). It claims not
to be able to lock a file..
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
[where a.b.c.d is our NFS server]
/sbin/rpc.statd is running on both client and server, and with a 2.4
kernel on the client (as the only change) GNOME logins and the lockf()
test program work just fine.
Any ideas? I'm stumped at this point.
Cheers,
Matt
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6: can't lockf() over NFS
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
1 sibling, 0 replies; 5+ messages in thread
From: Trond Myklebust @ 2003-11-26 0:39 UTC (permalink / raw)
To: Matt Bernstein; +Cc: linux-kernel
>>>>> " " == Matt Bernstein <mb/lkml@dcs.qmul.ac.uk> writes:
> I can't get Debian testing to log in to GNOME when home
> directories are mounted over NFS (Linux 2.6 client -> Linux
> 2.4-ac server). It claims not to be able to lock a file..
IIRC Debian had some issues with rpc.statd. They were using some
incorrect compilation options. Try grabbing a newer version from
'unstable'.
Cheers,
Trond
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6: can't lockf() over NFS
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
1 sibling, 2 replies; 5+ messages in thread
From: Chris Wright @ 2003-11-26 0:55 UTC (permalink / raw)
To: Matt Bernstein; +Cc: linux-kernel
* Matt Bernstein (mb/lkml@dcs.qmul.ac.uk) wrote:
> I can't get Debian testing to log in to GNOME when home directories are
> mounted over NFS (Linux 2.6 client -> Linux 2.4-ac server). It claims not
> to be able to lock a file..
>
> 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
>
> [where a.b.c.d is our NFS server]
>
> /sbin/rpc.statd is running on both client and server, and with a 2.4
> kernel on the client (as the only change) GNOME logins and the lockf()
> test program work just fine.
>
> Any ideas? I'm stumped at this point.
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.
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6: can't lockf() over NFS
2003-11-26 0:55 ` Chris Wright
@ 2003-11-26 1:35 ` Trond Myklebust
2003-11-26 11:21 ` Matt Bernstein
1 sibling, 0 replies; 5+ messages in thread
From: Trond Myklebust @ 2003-11-26 1:35 UTC (permalink / raw)
To: Chris Wright; +Cc: Matt Bernstein, linux-kernel
>>>>> " " == Chris Wright <chrisw@osdl.org> writes:
> 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
Sorry, yes. That one slipped my mind...
Cheers,
Trond
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6: can't lockf() over NFS
2003-11-26 0:55 ` Chris Wright
2003-11-26 1:35 ` Trond Myklebust
@ 2003-11-26 11:21 ` Matt Bernstein
1 sibling, 0 replies; 5+ messages in thread
From: Matt Bernstein @ 2003-11-26 11:21 UTC (permalink / raw)
To: Chris Wright; +Cc: linux-kernel
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 :)
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-11-26 11:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).