IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: A proposal for OPEN
On 25 Sep 2003, Joseph Galbraith <galb-list%vandyke.com@localhost> wrote:
> I've heard these terms before, but I'm not sure I've had them
> clearly defined for me before. Let me see if I'm anyplace close
> on what they mean :-)
>
> Mandatory Lock
> ==============
> Once I am granted a mandatory lock, I own it until
> I release it. Others trying to access the file in
> a way that conflicts with my lock will receive an
> error.
>
> Advisory Lock
> =============
> Once I am granted an advisory lock, I own it until
> either I release it or the server notifies me that
> it is breaking my lock. Others trying to access the
> file in a way that conflicts with my lock will result
> in the server breaking my lock.
This is closer to what is called an "opportunistic lock/oplock" in
CIFS, or "reservation" in NFS4.
Adding oplocks implies that the server must be able to initiate
notifications to the client, and to discover and recover from network
partitions or hung clients. It's quite complex.
--
Martin
linux.conf.au -- Adelaide, January 2004
Home |
Main Index |
Thread Index |
Old Index