From: Jeremy Sanders <jss@ast.cam.ac.uk>
Subject: Re: Locking from Tru64
Date: Wed, 5 Feb 2003 15:19:54 +0000 (GMT)
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <Pine.LNX.4.53.0302051517390.1790@xpc1.ast.cam.ac.uk>
References: <Pine.LNX.4.53.0302041525090.22528@xpc1.ast.cam.ac.uk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: nfs@lists.sourceforge.net
In-Reply-To: <Pine.LNX.4.53.0302041525090.22528@xpc1.ast.cam.ac.uk>
Errors-To: nfs-admin@lists.sourceforge.net

On Tue, 4 Feb 2003, Jeremy Sanders wrote:

> I have got an additional problem which I don't understand. We're locking
> mail spools over NFS from a Tru64 5.1B client machine to Linux
> 2.4.18-17.7.x (RedHat) server. Using a simple C program which opens the
> file, does lockf (fd, F_LOCK, 1)) and then closes it after 10 seconds,
> some users are able to lock their mail spool (one seen, actually) and many
> users are unable!

As an additional point of data, if the user who can lock their mail spool
copies the file to another file _with exactly the same permissions and
ownership_, then they are unable to lock this new file!

This behaviour seems bizarre and it's the linux server which isn't
replying with a

15:04:37.125897 linux.799 > tru64.1035:  udp 136 (DF)

response, so I'd guess it's a Linux specific problem.

Jeremy

-- 
Jeremy Sanders <jss@ast.cam.ac.uk>   http://www-xray.ast.cam.ac.uk/~jss/
X-Ray Group, Institute of Astronomy, University of Cambridge, UK.
Public Key Server PGP Key ID: E1AAE053


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs