From: mb/nfs@dcs.qmul.ac.uk
Subject: Re: trouble with file locking
Date: Mon, 24 Nov 2003 14:24:28 +0000 (GMT)
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <Pine.LNX.4.58.0311241416240.7849@lucy.dcs.qmul.ac.uk>
References: <20031112105043.020c1548.erik@thiele-hydraulik.de>
 <Pine.LNX.4.58.0311191259400.846@lewis.et.byu.edu> <shsd6bohzxw.fsf@charged.uio.no>
 <20031120070531.7886de98.erik@thiele-hydraulik.de> <16316.23490.266052.855506@charged.uio.no>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: nfs@lists.sourceforge.net
In-Reply-To: <16316.23490.266052.855506@charged.uio.no>
Errors-To: nfs-admin@lists.sourceforge.net

On Nov 20 Trond Myklebust wrote:

>Then you have been using POSIX locks (i.e. fcntl()/lockf()). They
>should work fine.

Possibly unrelated [hence CC trimmed]:

I can't get Debian testing to log in to GNOME when home directories are
mounted over NFS (Linux 2.6-mm 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 work just fine.

Any ideas? I'm stumped at this point.

Cheers,

Matt


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs